On Wednesday, 26. April 2006 16:53, Brad King wrote:
> Use set_target_properties to set the COMPILE_FLAGS property on each target.
Thanks, that seems to work nicely.
--
Dirk//\
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kd
Hi,
Previously we had an "install-exec" target for make which installed
only libraries and applications (and modules of course). This is very
handy if you have lot of data that does not change, but you have to
install the executables often as it will take much less time (even if
the timestamp
Hi,
I'm getting this cool error:
Building CXX object
kabc/plugins/file/CMakeFiles/kabc_file.dir/resourcefileconfi
g.obj
resourcefileconfig.cpp
Linking CXX shared library ..\..\..\bin\kabc_file.dll
LINK : ..\..\..\bin\kabc_file.dll not found or not built by the last
incremental
link; performing f
Andras Mantia wrote:
> Previously we had an "install-exec" target for make which installed
>only libraries and applications (and modules of course). This is very
>handy if you have lot of data that does not change, but you have to
>install the executables often as it will take much less time (even
On Friday 28 April 2006 15:23, you wrote:
> Andras Mantia wrote:
> > Previously we had an "install-exec" target for make which installed
> >only libraries and applications (and modules of course). This is
> > very handy if you have lot of data that does not change, but you
> > have to install the e
(Please CC to me as I am not a member of kde-buildsystem)
In Kopete (kdenetwork/kopete/protocols/jabber/libiris to be more precise), I
have some files where both header and implementation has the Q_OBJECT.
The Makefile.am used this trick:
s5b.lo: s5b.moc
CLEANFILES = s5b.moc
s5b.moc: $(srcdir)
On Friday, 28. April 2006 14:30, Andras Mantia wrote:
> It already does that (as I understood starting from cmake 2.4.0), but it
> still prints out everything, even if it's not installed for real, and
> this is slow, for example in KDevelop, as it processes all the output.
> If it doesn't print wh
On Friday 28 April 2006 16:07, Dirk Mueller wrote:
> On Friday, 28. April 2006 14:30, Andras Mantia wrote:
> > It already does that (as I understood starting from cmake 2.4.0),
> > but it still prints out everything, even if it's not installed for
> > real, and this is slow, for example in KDevelop
On Friday 28 April 2006 14:46, Michaël Larouche wrote:
> (Please CC to me as I am not a member of kde-buildsystem)
>
> In Kopete (kdenetwork/kopete/protocols/jabber/libiris to be more precise),
> I have some files where both header and implementation has the Q_OBJECT.
>
> The Makefile.am used this
Am Freitag, 28. April 2006 18:07 schrieb Alexander Neundorf:
> Doesn't this give a cyclic dependency ?
> s5b.moc depends on s5b.cpp, and s5b.cpp depends on s5b.moc because it
> includes it ?
Wow, I thought you was beyond that :)
s5b.cpp does not depend on s5b.moc, s5b.o does.
Greetings, Stephan
At 02:26 PM 4/28/2006, Thiago Macieira wrote:
>Kuba Ober wrote:
>>Couldn't agree more, especially that I'm migrating some more build stuff
>> at work to cmake. Cmake and Qt are the only dependencies for the
>> product in question, I'd consider it weird at least to add pkg-config
>> to the mix if a
William A. Hoffman wrote:
>Is that the Trolltech recommended way for windows and the Mac?
>If Trolltech required that pkg-config be installed before QT could
>be used on any platform, I would have no problem using it.
Qt doesn't require anything found with pkg-config to build. It's pointless
to r
At 04:19 PM 4/28/2006, Thiago Macieira wrote:
>William A. Hoffman wrote:
>>Is that the Trolltech recommended way for windows and the Mac?
>>If Trolltech required that pkg-config be installed before QT could
>>be used on any platform, I would have no problem using it.
>
>Qt doesn't require anything
William A. Hoffman wrote:
>>But we do recommend using pkg-config for finding Qt/X11. Not qmake.
>> qmake is a separate program that doesn't have to be installed to use
>> or develop with Qt.
>
>That is a surprise.I thought that qt used qmake as part of its own
>build process, and put qmake into
On Friday 28 April 2006 23:57, Thiago Macieira wrote:
...
> They either use qmake themselves, or their own buildsystems (which means
> they don't use qmake).
>
> Cmake is the only buildsystem that depends on another buildsystem being
> installed (qmake) for it to work. What the FindQt4.cmake script
SVN commit 535237 by neundorf:
-check where some of the results are used
it seems there are quite a lot of checks which aren't used anywhere
CCMAIL: kde-buildsystem@kde.org
I moved the (seemingly) unused checks at the of the file, I guess they can be
removed.
Do we want modular configuration ?
16 matches
Mail list logo