-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
again, more build errors. How come some people report problemless builds? ;)
Anyway, while building kdeui:
Building CXX object kdecore/CMakeFiles/kdecore.dir/kacceleratormanager.obj
kacceleratormanager.cpp
On Wednesday 29 March 2006 16:02, Maarten Th. Mulders wrote:
Hi all,
again, more build errors. How come some people report problemless builds? ;)
Anyway, while building kdeui:
Building CXX object kdecore/CMakeFiles/kdecore.dir/kacceleratormanager.obj
kacceleratormanager.cpp
Hi,
today (after a week or so not trying to compile), I get this error:
[EMAIL PROTECTED]:~/KDE/build/kdelibs cmake ../../kdelibs
kdelibs requires an out of source build. Please create a separate build \
directory and run 'cmake path_to_kdelibs [options]' there.
-- Configuring done
At 10:49 AM 3/29/2006, you wrote:
When a build tree is first created by CMake it becomes locked to the
compiler specified the first time. If the compiler is not specified
with a full path then the PATH is searched to find it, and then that
full path is used. It is not safe to build some of a
Thiago Macieira wrote:
Brad King wrote:
When a build tree is first created by CMake it becomes locked to the
compiler specified the first time. If the compiler is not specified
with a full path then the PATH is searched to find it, and then that
full path is used. It is not safe to build some
On Wed, Mar 29, 2006 at 05:21:01PM +, Kurt Pfeifle wrote:
Hi,
today (after a week or so not trying to compile), I get this error:
[EMAIL PROTECTED]:~/KDE/build/kdelibs cmake ../../kdelibs
kdelibs requires an out of source build. Please create a separate build \
directory
On Wednesday 29 March 2006 02:09, Craig Bradney wrote:
Hi,
I'm attempting to convert Scribus to use cmake, as we want to escape
autohell too :) so.. I'm making progress but am stuck for examples on some
basics. Its been suggested I would find the most information on this list.
The first one
On Wednesday 29 March 2006 21:01, Thiago Macieira wrote:
Brad King wrote:
When a compilation error prevents some library A from building then any
library B that depends on (links to) library A will not attempt to
build. Technically library B's object files could be built but library
B could
On 3/29/06, Kurt Pfeifle [EMAIL PROTECTED] wrote:
My cmake path_to_kdelibs uses a relative path though -- could that
be an issue?
No, a relative path there should be completely fine.
I wonder if there is some sort of limit on the cmake string compare
functions. How long is the full path to
On Wednesday 29 March 2006 19:21, Kurt Pfeifle wrote:
Hi,
today (after a week or so not trying to compile), I get this error:
[EMAIL PROTECTED]:~/KDE/build/kdelibs cmake ../../kdelibs
kdelibs requires an out of source build. Please create a separate build \
directory and run
On Wednesday 29 March 2006 18:44, Matt Rogers wrote:
On Wed, Mar 29, 2006 at 05:21:01PM +, Kurt Pfeifle wrote:
Hi,
today (after a week or so not trying to compile), I get this error:
[EMAIL PROTECTED]:~/KDE/build/kdelibs cmake ../../kdelibs
kdelibs requires an out of source
On Wednesday 29 March 2006 20:54, Alexander Neundorf wrote:
On Wednesday 29 March 2006 19:21, Kurt Pfeifle wrote:
Hi,
today (after a week or so not trying to compile), I get this error:
[EMAIL PROTECTED]:~/KDE/build/kdelibs cmake ../../kdelibs
kdelibs requires an out of source
On Wednesday 29 March 2006 22:22, Bill Hoffman wrote:
At 11:04 AM 3/28/2006, David Faure wrote:
Any reason why we get two mails with 10s interval for each failing build,
BTW?
The only difference seems to be
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL
PROTECTED],
At 03:31 PM 3/29/2006, David Faure wrote:
=an email sent. The subject line should be different, dash17 or matt.rogers.
Yes. But I was getting two from dash17 and two from matt.rogers.
The To line could also be simplified :)
I think that should be fixed now. Lets see what happens the next
Hi,
On Wednesday 29 March 2006 02:34, Michael Biebl wrote:
Compiling kdebase against kdelibs4_snapshot failed at four places for
me because of missing headers. (Xcursor/Xrender headers were not
found).
I added X11_Xcursor_INCLUDE_PATH/X11_Xrender_INCLUDE_PATH to the
include path for the
Hi, CMake devleopers,
I found ccmake a quite good approach to make the configure setup for
cmake more compile newbie-user friendly. Thank you for that!
Here are two suggestions to improve it even further:
* It recently happened that I came back to a screen session with
2 windows open where I
On Wednesday 29 March 2006 20:34, Tanner Lovelace wrote:
On 3/29/06, Kurt Pfeifle [EMAIL PROTECTED] wrote:
My cmake path_to_kdelibs uses a relative path though -- could that
be an issue?
No, a relative path there should be completely fine.
I wonder if there is some sort of limit on the
At 04:22 PM 3/29/2006, Kurt Pfeifle wrote:
[EMAIL PROTECTED]:~/src/kde40svn/trunk/KDE/build/kdelibs hostname -f
nx.openusability.org
[EMAIL PROTECTED]:~/src/kde40svn/trunk/KDE/build/kdelibs pwd
/home/kdev4/src/kde40svn/trunk/KDE/build/kdelibs
[EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, rebuild Qt 4.1.1 with the patches you mentioned. Building dcop.exe
now fails with:
Linking CXX executable ..\..\bin\dcop.exe
dcop.obj : error LNK2019: unresolved external symbol
__declspec(dllimport) public: bool __thiscall
Paulo Jorge Guedes schrieb:
-Original Message-
From: William A. Hoffman [mailto:[EMAIL PROTECTED]
Sent: quarta-feira, 29 de Março de 2006 15:42
To: kde-buildsystem@kde.org
Subject: Re: Build errors
What is the current status of the windows build?
Is it time to set up a dashboard?
Maarten Th. Mulders schrieb:
Well, rebuild Qt 4.1.1 with the patches you mentioned. Building dcop.exe
now fails with:
Linking CXX executable ..\..\bin\dcop.exe
dcop.obj : error LNK2019: unresolved external symbol
__declspec(dllimport) public: bool __thiscall QUrl::hasQuery(void)const
On Thursday 30 March 2006 02:49, you wrote:
unresolved external symbol
__declspec(dllimport) public: bool __thiscall QUrl::hasQuery(void)const
That's what the qt-copy patches add. If it's not there, then you didn't apply
all the patches, or you didn't rebuild Qt, or it's finding another Qt on
22 matches
Mail list logo
