On Thursday 23 March 2006 01:21, Brad King wrote:
both - (not on OS X)
I really don't like this option.
Me neither. Alex, can we remove it?
FYI, I anticipated this dilemma and provided a preinstall target that
can be built by the user to do the relinking before changing to root:
make
On Wednesday, 22. March 2006 18:42, Alexander Neundorf wrote:
Dirk, why is this required for you ?
It really shouldn't.
I don't see how, there are no rpaths anywhere, and it only finds the installed
KDE 3 libraries (because they have the same SONAME, which is a bug on its own
I'm currently
William A. Hoffman wrote:
qt-copy should have a different version number. Then we can make sure
we get the right version for kde. But, as it is now, you can not tell
the difference from qt-copy qmake and qmake from qt 4.1.1.
You can't do that because we don't know yet which version number
-Original Message-
From: Christian Ehrlicher [mailto:[EMAIL PROTECTED]
Sent: quarta-feira, 22 de Março de 2006 21:15
To: kde-buildsystem@kde.org
Subject: Re: kdewin32 build error
Is it possible to build and install qt-copy on Windows? It has the
patches applied or it has to be
-Original Message-
From: Paulo Jorge Guedes [mailto:[EMAIL PROTECTED]
Sent: quinta-feira, 23 de Março de 2006 11:38
To: kde-buildsystem@kde.org
Subject: RE: kdewin32 build error
-Original Message-
From: Christian Ehrlicher [mailto:[EMAIL PROTECTED]
Sent: quarta-feira,
On Thu, Mar 23, 2006 at 10:33:06AM +0100, Thiago Macieira wrote:
Michael Olbrich wrote:
$ ls `qmake -query QT_INSTALL_BINS`/uic
/home/tjmaciei/troll/qt-4.1-build/bin/uic*
$ ls `pkg-config --variable prefix QtCore`/bin/uic
/home/tjmaciei/troll/qt-4.1-build/bin/uic*
That is not
Michael Olbrich wrote:
What I mean is, it _can_ be changed. Debian has modified
mkspecs/linux-g++/qmake.conf:
QMAKE_MOC = $$[QT_INSTALL_BINS]/moc-qt4
QMAKE_UIC = $$[QT_INSTALL_BINS]/uic-qt4
The question is, how can a buildsystem like cmake figure out which
moc/uic
At 10:19 AM 3/23/2006, you wrote:
just linux. i don't have a seperate windows machine here to test on.
Hey cool, it worked, I can see your continuous build. What type
of machine is that? It built in 45 minutes?
-Bill
___
Kde-buildsystem mailing
On Thu, Mar 23, 2006 at 11:51:26AM -0500, William A. Hoffman wrote:
At 10:19 AM 3/23/2006, you wrote:
just linux. i don't have a seperate windows machine here to test on.
Hey cool, it worked, I can see your continuous build. What type
of machine is that? It built in 45 minutes?
It's
Matt Rogers wrote:
If i use ccmake to configure the build and change
CMAKE_VERBOSE_MAKEFILE to OFF, the setting has no effect and I have to
manually edit the CMakeLists.txt file in order to turn off verbosity. Is
this the intended effect?
This is because the top level CMakeLists.txt file in
At 01:30 PM 3/23/2006, Matt Rogers wrote:
On Thu, Mar 23, 2006 at 11:51:26AM -0500, William A. Hoffman wrote:
At 10:19 AM 3/23/2006, you wrote:
just linux. i don't have a seperate windows machine here to test on.
Hey cool, it worked, I can see your continuous build. What type
of machine
On Thursday 23 March 2006 02:03, Matt Rogers wrote:
Hi,
I'd like to start working on native CMake support for KDevelop 4. What I
mean by this is that when you open a project that is set up to use CMake,
the CMakeLists.txt files plus any additional cmake macros are automatically
loaded in and
On Thursday 23 March 2006 19:36, David Faure wrote:
On Thursday 23 March 2006 19:33, Matt Rogers wrote:
Hi!
If i use ccmake to configure the build and change
CMAKE_VERBOSE_MAKEFILE to OFF, the setting has no effect and I have to
manually edit the CMakeLists.txt file in order to turn off
Alexander Neundorf wrote:
On Thursday 23 March 2006 02:03, Matt Rogers wrote:
Hi,
I'd like to start working on native CMake support for KDevelop 4. What I
mean by this is that when you open a project that is set up to use CMake,
the CMakeLists.txt files plus any additional cmake macros are
One more thing, I just added this:
KDE4_BUILD_TESTS:BOOL=ON
To both my nightly and continuous builds so that the tests will be run as well.
-Bill
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
On Thursday, 23. March 2006 20:17, William A. Hoffman wrote:
KDE4_BUILD_TESTS:BOOL=ON
To both my nightly and continuous builds so that the tests will be run as
well.
Most of the tests should fail though as they require a running system, which
you're unlikely to have on a dashboard
On Thu, Mar 23, 2006 at 07:55:35PM +0100, David Faure wrote:
On Thursday 23 March 2006 19:34, William A. Hoffman wrote:
At 01:33 PM 3/23/2006, Matt Rogers wrote:
Hi!
If i use ccmake to configure the build and change
CMAKE_VERBOSE_MAKEFILE to OFF, the setting has no effect and I have to
At 02:36 PM 3/23/2006, Dirk Mueller wrote:
On Thursday, 23. March 2006 20:17, William A. Hoffman wrote:
KDE4_BUILD_TESTS:BOOL=ON
To both my nightly and continuous builds so that the tests will be run as
well.
Most of the tests should fail though as they require a running system, which
this, or do
you have to install to run the tests?
Well, looks like the test do not even build right now. :(
http://public.kitware.com/KDE/Testing/Sites/matt.rogers.name/Linux-Archlinux-gcc4.0.3/20060323-1939-Continuous/BuildError.html
-Bill
___
Kde
/matt.rogers.name/Linux-Archlinux-gcc4.0.3/20060323-1939-Continuous/BuildError.html
khtml's testregression is a rather special build, a developer tool in a way.
It shouldn't be built by default, but rather by a special target.
In the old buildsystem this would mean make check wouldn't build it,
but make
At 06:43 PM 3/23/2006, David Faure wrote:
I fixed the katepart regression test to not run it when kdelibs isn't
installed yet,
let's see if that was enough.
http://public.kitware.com/KDE/Testing/Sites/matt.rogers.name/Linux-Archlinux-gcc4.0.3/20060323-1939-Continuous/BuildError.html
khtml's
cmake/modules/CMakeLists.txt in kdelibs4_snapshot still references
kde3init_dummy.cpp.in which makes make install fail. It would be a
good idea imo to merge back the changes from trunk where this seems to
be fixed already.
Michael
___
Kde-buildsystem
22 matches
Mail list logo
