Am Mittwoch, 21. Februar 2007 23:31 schrieb Thiago Macieira:
Alexander Neundorf wrote:
If I link some compiled headers without -no-undefined, it seems to work.
Am I missing something ?
Basically we want to:
==
#define QT_NO_CAST_FROM_ASCII
#define QT_NO_CAST_TO_ASCII
#define
Am Donnerstag, 22. Februar 2007 00:21 schrieb Brad King:
For the VS IDE generators there does not seem to be a way to compile
sources without archiving them, but since the objects contain only a few
symbols they should not be too big.
It's not necessary to do this for any but one platform, so
Stephan Kulow wrote:
It's even worse. Linking will break in some cases
Oh? I would think they should all compile and link.
What were those linking errors? Were they justified?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
Am Donnerstag, 22. Februar 2007 10:51 schrieb Thiago Macieira:
Stephan Kulow wrote:
It's even worse. Linking will break in some cases
Oh? I would think they should all compile and link.
What were those linking errors? Were they justified?
I'm not expert enough to tell you if they are
On Thursday, 22. February 2007 10:51, Thiago Macieira wrote:
What were those linking errors? Were they justified?
In some cases, they are, like for example virtual inline functions. In some
other cases, they were not (missing #include caused gcc to interpret type
attributes as instantiation
On Thursday, 22. February 2007 11:17, Dirk Mueller wrote:
Is there some (undocumented) way of getting rid of all this fancy stuff
that nobody needs?
To be more precise:
I don't want it to output progress information when it might not have done
anything heavy. for example the Built target
On Thursday 22 February 2007 11:28, Dirk Mueller wrote:
On Thursday, 22. February 2007 11:17, Dirk Mueller wrote:
Is there some (undocumented) way of getting rid of all this fancy stuff
that nobody needs?
To be more precise:
I don't want it to output progress information when it might not
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
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
Christian Ehrlicher wrote:
pkg-config on win32 is a bad idea... :(
If you want to compile KDE with Qt 4.3, you'll need it.
kdelibs does not build because QtUiTools is missing a dependency when
linking kjsembed.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Von: Thiago Macieira [EMAIL PROTECTED]
Christian Ehrlicher wrote:
pkg-config on win32 is a bad idea... :(
If you want to compile KDE with Qt 4.3, you'll need it.
kdelibs does not build because QtUiTools is missing a dependency when
linking kjsembed.
Can't we get around this problem by
[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
Von: Thiago Macieira [EMAIL PROTECTED]
[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
13 matches
Mail list logo
