Re: Qt static libraries - pkgconfig again
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. > >This sounds like that it's easier to patch Qt than to introduce > pkg-config on windows, or I'm wrong? Yes, it's easier to patch it. But that doesn't mean the Trolls will accept it. Thay made it specifically static for a reason. I just don't know what reason that is. And I kind of doubt that the reason is gone. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 pgptn2qk94LYl.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
On Friday 23 February 2007 23:18:04 Christian Ehrlicher wrote: > Holger Schröder schrieb: > > On Friday 23 February 2007 21:38:56 Thiago Macieira wrote: > >> Simon Hausmann wrote: > >>> Christian is right there, also because qmake does not generate > >>> pkg-config files on Windows. > >> > >> May I suggest then that we together standardise on a dependency file for > >> static libraries (and platforms where such a thing is necessary)? More > >> or less like the libtool .la file. > >> > >> CMake will need it anyways for supporting static builds of other > >> applications. > > > > well, pkg-config is available on win32, at least that is what > > http://pkgconfig.freedesktop.org/wiki/ says, although i haven´t tested it > > yet. > > > > so what about this option: for qt 4.2 we leave things as they are, and > > for qt 4.3 the trolls install .pc files on windows too, and we use them > > under linux and under windows ? > > pkg-config is available on win32, but it's only used in msys environment > (where you have a linux-like directory layout) -> the location of the pc > files is not defined on windows. A path can be added with > PKG_CONFIG_PATH (afaik), but imho this just makes the whole kde > compilation more complex than we gain advantages from using pkg-config > on win32. > perhaps we should keep the future in mind. i think it would be good, if we agree on a directory layout for the installation of kde on windows under a prefix. but the user should be able to unpack the kde package into any directory on the windows machine and have a working installation. and right now there are still some limitations in kde, which make this impossible, like the paths in kde4-config are hardcoded. perhaps pkg-config could help us there too. > Christian Holger ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
Thiago Macieira wrote: > [EMAIL PROTECTED] wrote: >>> kdelibs does not build because QtUiTools is missing a dependency when >>> linking kjsembed. >> 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. This sounds like that it's easier to patch Qt than to introduce pkg-config on windows, or I'm wrong? > >> Or by parsing the .prl-files. > > That would not be recommended. Those files are not documented anywhere and > could change format any time. > >> Can't qmake tell us what deps we need? > > I guess it could. But there doesn't seem to be an easy way of doing that. > >> What depenency is missing? > > QtScript. > >> I need to compile qt4.3 on win32 to see if we really need to add this >> dependency - can you tell me more what's missing? >> >> The directory layout on win32 does not allow a pkg-config tool as every >> program has it's own subdirectory without a common place for >> .pkg-config - files. We've enough problems with other external >> libs/tools on win32 - adding another one would just rise the level for >> new devs once more :( > > We can use pkg-config for Qt only, at least. Fortunately, none of the Qt > library .pc files has external dependencies, so they will parse easily by > pkg-config with just one dir in $PKG_CONFIG_PATH. > > In any case, shouldn't Windows start having a common pkgconfig path then? > > > > > > ___ > Kde-buildsystem mailing list > Kde-buildsystem@kde.org > https://mail.kde.org/mailman/listinfo/kde-buildsystem -- Peter Kümmel ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
Holger Schröder schrieb: On Friday 23 February 2007 21:38:56 Thiago Macieira wrote: Simon Hausmann wrote: Christian is right there, also because qmake does not generate pkg-config files on Windows. May I suggest then that we together standardise on a dependency file for static libraries (and platforms where such a thing is necessary)? More or less like the libtool .la file. CMake will need it anyways for supporting static builds of other applications. well, pkg-config is available on win32, at least that is what http://pkgconfig.freedesktop.org/wiki/ says, although i haven´t tested it yet. so what about this option: for qt 4.2 we leave things as they are, and for qt 4.3 the trolls install .pc files on windows too, and we use them under linux and under windows ? pkg-config is available on win32, but it's only used in msys environment (where you have a linux-like directory layout) -> the location of the pc files is not defined on windows. A path can be added with PKG_CONFIG_PATH (afaik), but imho this just makes the whole kde compilation more complex than we gain advantages from using pkg-config on win32. Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
On Friday 23 February 2007 21:38:56 Thiago Macieira wrote: > Simon Hausmann wrote: > >Christian is right there, also because qmake does not generate > > pkg-config files on Windows. > > May I suggest then that we together standardise on a dependency file for > static libraries (and platforms where such a thing is necessary)? More or > less like the libtool .la file. > > CMake will need it anyways for supporting static builds of other > applications. well, pkg-config is available on win32, at least that is what http://pkgconfig.freedesktop.org/wiki/ says, although i haven´t tested it yet. so what about this option: for qt 4.2 we leave things as they are, and for qt 4.3 the trolls install .pc files on windows too, and we use them under linux and under windows ? just my 2c, Holger ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
Simon Hausmann wrote: >Christian is right there, also because qmake does not generate > pkg-config files on Windows. May I suggest then that we together standardise on a dependency file for static libraries (and platforms where such a thing is necessary)? More or less like the libtool .la file. CMake will need it anyways for supporting static builds of other applications. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 pgpIVtNqUybyS.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
Am Freitag, 23. Februar 2007 19:41 schrieb Thiago Macieira: > [EMAIL PROTECTED] wrote: > >> I guess it could. But there doesn't seem to be an easy way of doing > >> that. > > > >maybe we should ask the trolls here - it looks quite easy to make qmake > > parse the .prl-files and print out QMAKE_PRL_LIBS. > > I think that's pointless. If we're going to parse a file, we can just as > well parse the .pc file, which we are guaranteed to be standard. .. that only exists on unix. Greetings, Stephan ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
David Faure wrote: >For this one special case, can't we start linking to -lQtUiTools > -lQtScript when we switch to 4.3, rather than complicate the setup on > all platforms and especially on windows? That means that I and all other people who are testing Qt 4.3 right now must patch our kdelibs and keep uncommitted changes. It is also true that KDE will require Qt 4.3 when it's released. But other users of FindQt4.cmake won't, so we can't add that dependency automatically. FindQt4.cmake has to work with both versions. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 pgpmtXLiG4B7c.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
[EMAIL PROTECTED] wrote: >> I guess it could. But there doesn't seem to be an easy way of doing >> that. > >maybe we should ask the trolls here - it looks quite easy to make qmake > parse the .prl-files and print out QMAKE_PRL_LIBS. I think that's pointless. If we're going to parse a file, we can just as well parse the .pc file, which we are guaranteed to be standard. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 pgpoYHLUSneTj.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
On Friday 23 February 2007 06:32:03 Christian Ehrlicher wrote: > Thiago Macieira schrieb: > > Qt has one static library that we use in KDE code: QtUiTools. Whichever > > reason the Trolls had to make it static is besides the point: it is > > static. > > > > That means we must fetch its dependency info from the Qt installation > > into CMake. And Qt provides only one official way of doing that: via > > pkg-config. > > > > So, I ask again: can we start supporting discovery of Qt via pkg-config > > by default on all systems? If that doesn't work, we'd have a fallback to > > the current discovery via qmake. > > pkg-config on win32 is a bad idea... :( Christian is right there, also because qmake does not generate pkg-config files on Windows. I think for now we should either do what David suggests and just hardcode it for 4.3 or maybe use pkg-config on !windows and hardcode it only on Windows. Simon pgpAqNfcL41v6.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Qt static libraries - pkgconfig again
On Friday 23 February 2007, Thiago Macieira wrote: > > What depenency is missing? > > QtScript. > For this one special case, can't we start linking to -lQtUiTools -lQtScript when we switch to 4.3, rather than complicate the setup on all platforms and especially on windows? -- David Faure, [EMAIL PROTECTED], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
