Re: Reducing excess linkage - cmake 2.6 IMPORTED targets and LINK_INTERFACE_LIBRARIES for kdelibs

2008-06-30 Thread Leo Savernik
Am Montag, 30. Juni 2008 schrieb Modestas Vainius: > 2) KDE 4.1 branch will be more compatible with older 3rd party kde4   > applications. Please have in mind that this experimental linking will > probably be enabled by some distros (Debian at least however we are not > going to ship full KDE 4.1 i

Re: How to find qmake to find QT4

2006-03-22 Thread Leo Savernik
Am Dienstag, 21. März 2006 19:27 schrieb William A. Hoffman: [...] > My understanding was that QTDIR was being deprecated for qt4, and that > qmake had to be in the PATH. I can not find a reference on the qt site, > but there are several posts like this one floating around: > > http://lists.ibibli

Re: changes how Qt4 is found in trunk/kdelibs/

2006-04-05 Thread Leo Savernik
Am Mittwoch, 5. April 2006 19:11 schrieb Alexander Neundorf: > > I don't think it is just windows, and also this does make it harder to > > work with a non-installed qt, unless the user sets PKG_CONFIG_PATH and > > some other stuff, pkg-config will not even know about the users local > > qt install

Re: changes how Qt4 is found in trunk/kdelibs/

2006-04-06 Thread Leo Savernik
Am Mittwoch, 5. April 2006 22:27 schrieb William A. Hoffman: > At 02:58 PM 4/5/2006, you wrote: > >William A. Hoffman wrote: > >>Well, it is not installed on any of those machines that I have access > >> to. > > > >One example: > ># uname -a > >SunOS mimir 5.9 Generic_117171-17 sun4u sparc SUNW,Sun

Re: RPATH handling changed once again

2006-04-09 Thread Leo Savernik
Am Samstag, 8. April 2006 01:34 schrieb Alexander Neundorf: > kde4_add_executable(kconfig_compiler RUN_UNINSTALLED ${kcfgSources} ) > will be built with RPATH pointing to the source dir RPATH pointing to sourcedir? Shouldn't it be builddir? mfg Leo

Re: cmake colors

2006-04-19 Thread Leo Savernik
Am Mittwoch, 19. April 2006 16:10 schrieb Brad King: > This was not made clear in the original feature request, but it is easy > to fix.  So, to be clear, only the first word should be colored, and the > text attributes should be set to have a black background too.  Is this > correct? No, the back

Re: do we want to keep the out-of-source-only requirement ?

2006-04-30 Thread Leo Savernik
Am Sonntag, 30. April 2006 12:48 schrieb David Faure: > > Do we want to allow them again ? > > No (as the thread concluded), but maybe we could provide a way to make the > setup easier > > E.g. some script in the toplevel of the modules (autogen.sh?) could say > test -d build || mkdir build > c

Re: do we want to keep the out-of-source-only requirement ?

2006-04-30 Thread Leo Savernik
Am Sonntag, 30. April 2006 14:19 schrieb David Faure: > > Recent versions of gcc support the same way to "emulate" an in-source > > build. This seems like a suitable approach to minimize troubles and > > complaints. > > How does it solve the toplevel Makefile problem? I think they use some configu

Re: Standalone qt-dbus in kdesupport

2006-06-09 Thread Leo Savernik
Am Freitag, 9. Juni 2006 10:08 schrieb Ralf Habacker: > rpmbuild uses > > make install prefix= Automake has also supported DESTDIR for ages which is prepended to the prefix at installation time. I've always used this one when preparing binary packages. Couldn't cmake simply take advantage of thi

Re: [PATCH] Add GENERATE_MOC optional parameter in kde4_add_kcfg_files

2006-07-05 Thread Leo Savernik
Am Mittwoch, 5. Juli 2006 11:20 schrieb Alexander Neundorf: > Can it be detected whether there is moc required ? > If so, there would have to be a small cmake script which is called during > build time (i.e. not cmake time) which reads the input file and the > produces the moc stuff is required. Mo

Re: patch: c/cxxflags for static libraries

2006-07-19 Thread Leo Savernik
Am Mittwoch, 19. Juli 2006 17:06 schrieb Matt Broadstone: > What I am referring to is that when I'm working on khtml (in this > example) and make a change to say dom/, in my build dir I can cd to > kdelibs/build/khtml/dom and build from that directory instead of the > khtml directory and it will on

Re: RFC: automoc changes

2006-11-05 Thread Leo Savernik
Am Sonntag, 5. November 2006 13:48 schrieb Alexander Neundorf: > BUT you now have to use the kde4_add_* functions. Just being curious: If I want to develop a kde4 app/lib, is there any compelling use case not to use the kde4_* macros? Concerning the options, I'd simply expect the kde4_* macros p

Re: KDE/kdemultimedia

2007-01-28 Thread Leo Savernik
Am Sonntag, 28. Januar 2007 schrieb Matthias Kretz: > On Sunday 28 January 2007 11:25, Tim Beaulen wrote: > > Disable JuK from compiling, it conflicts with TagLib > > You mean that both taglib and JuK have an include called tag.h? Even though > juk uses #include it picks up the one from juk and no

Re: Qt static libraries - pkgconfig again

2007-02-24 Thread Leo Savernik
Am Samstag, 24. Februar 2007 schrieb Thiago Macieira: > Peter Kümmel wrote: > >>> Can't we get around this problem by convincing the trolls to not make > >>> it a static lib? > >> > >> I doubt that. QtUiTools is a very small library whose purpose is to > >> load designer-generated .ui files. > > >

Re: Qt static libraries - pkgconfig again

2007-02-26 Thread Leo Savernik
Am Sonntag, 25. Februar 2007 schrieb Thiago Macieira: > $ tail -n 5 tools/designer/src/lib/uilib/uilib.pri > !contains(DEFINES, QT_FORMBUILDER_NO_SCRIPT) { >     QT += script >     HEADERS += $$PWD/formscriptrunner_p.h >     SOURCES += $$PWD/formscriptrunner.cpp > } > > Which, BTW, also shows that