Error compiling kdeartwork SVN TRUNK: You cannot use Qt 4 .ui-files with Qt/KDE 3!

Martijn Klingens klingens at kde.org
Fri Jun 17 20:36:27 BST 2005


On Friday 17 June 2005 13:58, Chris Howells wrote:
> On Friday 17 June 2005 12:29, Steven P. Ulrick wrote:
> > Hello, Everyone :)
> > When compiling a fresh download of kdeartwork from SVN TRUNK, I got the
> >
> > following error:
> > > ERROR:kscreensaver/kdesavers/Makefile.am: Unknown UIC version for /
> > > home/steve/CVS/KDE-SVN/kdeartwork/kscreensaver/kdesavers/
> > > firesaversetup.ui. Rerun make -f Makefile.cvs. ERROR:kscreensaver/
> > > kdesavers/Makefile.am: You cannot use Qt 4 .ui-files with Qt/KDE 3!
> > > Please use a Qt 4-based build system.
> >
> > I followed the instructions quoted above, and did the following:
> > 1. Re-ran unsermake -f Makefile.cvs
> > 2. Then attempted to re-run ./configure & unsermake
>
> This is a bug in unsermake somewhere relating to Makefile.in generation.
> For some reason that file doesn't get added to QT3_UIFILES in Makefile.in
> and then the resulting Makefile is wrong also.
>
> I have been unable to work out why, e.g. what makes that file different to
> any others. fixuifiles reports no problem and resaving the file in designer
> doesn't fix it.

I think the conditional compilation of the GL screensavers causes troubles 
here. After a default configure I get the rather surprising:

    martijn at martijn:~/src/kde-head/kdeartwork/kscreensaver > bdcompile
    Running /usr/local/bin/unsermake compile...
    kscreensaver/kdesavers/Makefile.am: no rule to create target:
        ../kscreensaver/kdesavers/firesaversetup.moc(../kscreensaver/kdesavers/firesaversetup.o)

I.e. unsermake mistakenly thinks it needs a .moc file for code that should not 
be compiled in at all!

Moving the GL_SAVERS= line outside the if makes it all compile for me. (Didn't 
try linking or running as I have no interest in the screensavers, but 
compilation worked.)

I'm afraid you need someone who knows the stuff about conditional compilation 
though, it seems to be unrelated to the designer version detection. Coolo?

-- 
Martijn




More information about the kde-core-devel mailing list