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
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
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
-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 QUrl::hasQuery(void)
On Thursday 30 March 2006 00:36, Kurt Pfeifle wrote:
> On Wednesday 29 March 2006 21:42, Alexander Neundorf wrote:
> > On Wednesday 29 March 2006 23:22, Kurt Pfeifle wrote:
> > ...
> >
> > > [EMAIL PROTECTED]:~/src/kde40svn/trunk/KDE/build/kdelibs> echo $(cd
> > > ../../kdelibs;pwd) /home/kdev4/s
On Wednesday 29 March 2006 21:42, Alexander Neundorf wrote:
> On Wednesday 29 March 2006 23:22, Kurt Pfeifle wrote:
> ...
> > [EMAIL PROTECTED]:~/src/kde40svn/trunk/KDE/build/kdelibs> echo $(cd
> > ../../kdelibs;pwd) /home/kdev4/src/kde40svn/trunk/KDE/kdelibs
> >
> > [EMAIL PROTECTED]:~/src/kde
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 PROTECTED]:~/src/kde40svn
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
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 wher
On Wednesday 29 March 2006 23:22, Kurt Pfeifle wrote:
...
> [EMAIL PROTECTED]:~/src/kde40svn/trunk/KDE/build/kdelibs> echo $(cd
> ../../kdelibs;pwd) /home/kdev4/src/kde40svn/trunk/KDE/kdelibs
>
> [EMAIL PROTECTED]:~/src/kde40svn/trunk/KDE/build/kdelibs> cmake
> ../../kdelibs -- debug output for
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
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 nex
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
> >P
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
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 o
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], [EMAIL PROTECTED]
>in the first one.
>
>PS: is [EMAIL PROTE
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 r
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
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
> >
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 fir
On Tuesday 28 March 2006 23:11, Albert Astals Cid wrote:
> A Dimarts 28 Març 2006 23:04, David Faure va escriure:
> > On Tuesday 28 March 2006 21:36, Thiago Macieira wrote:
> > > Albert Astals Cid wrote:
> > > >That has worked for ages (since i began developing for KDE), is your
> > > >recommendati
On Wednesday 29 March 2006 18:41, 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 o
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 still not be linked under "make -k".
This is exactly what
Matt Rogers wrote:
> On Wed, Mar 29, 2006 at 07:38:07PM +0200, Thiago Macieira wrote:
>
>>I've also noticed that make -k isn't working in the cmake builds. Whenever
>>it finds an error, it halts the compilation completely, instead of
>>ignoring (like I told it to). What's even more interesting,
A Dimecres 29 Març 2006 09:32, Laurent Montel va escriure:
> On Tuesday 28 March 2006 19:37, Albert Astals Cid wrote:
> > A Dimarts 28 Març 2006 10:39, Laurent Montel va escriure:
> > > On Tuesday 28 March 2006 10:23, David Faure wrote:
> > > > On Monday 27 March 2006 21:26, Alexander Neundorf wrot
On Wed, Mar 29, 2006 at 07:38:07PM +0200, Thiago Macieira wrote:
> I've also noticed that make -k isn't working in the cmake builds. Whenever
> it finds an error, it halts the compilation completely, instead of
> ignoring (like I told it to). What's even more interesting, going to
> another dire
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 \
>direc
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 \
>direc
I've also noticed that make -k isn't working in the cmake builds. Whenever
it finds an error, it halts the compilation completely, instead of
ignoring (like I told it to). What's even more interesting, going to
another directory, completely unrelated to the error, also doesn't work.
Also, it's
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 b
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 of a tree with one
>co
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 o
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
> -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? I have not done so
At 10:15 AM 3/29/2006, Christian Ehrlicher wrote:
>William A. Hoffman schrieb:
>
>It compiled some time ago - currently I don't know because of the
>changes in khtml & kjs.
Which is why a dashboard build is needed. :)
-Bill
___
Kde-buildsystem maili
At 10:15 AM 3/29/2006, Christian Ehrlicher wrote:
>William A. Hoffman schrieb:
>> What is the current status of the windows build?
>> Is it time to set up a dashboard? I have not done so
>> yet, because it did not compile without errors. Should
>> kdelibs compile without errors on windows now?
>
Thiago Macieira wrote:
> Alexander Neundorf wrote:
>
>>I just successfully compiled kdelibs/ from trunk with "make -j4" on my
>>single processor machine.
>>Could you please verify that it also works for your setups ?
>>If there are problems, let me know.
>
> I tried a make -j25 on the compile far
William A. Hoffman schrieb:
> What is the current status of the windows build?
> Is it time to set up a dashboard? I have not done so
> yet, because it did not compile without errors. Should
> kdelibs compile without errors on windows now?
It compiled some time ago - currently I don't know becau
What is the current status of the windows build?
Is it time to set up a dashboard? I have not done so
yet, because it did not compile without errors. Should
kdelibs compile without errors on windows now?
-Bill
___
Kde-buildsystem mailing list
Kde-bui
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
> D:\sou
-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
D:\source\kde-svn\kdelibs\kdeui\kact
At 02:32 AM 3/29/2006, Laurent Montel wrote:
>So for me it's not logical.
>We specify PATH where to search and it searchs into at the end.
>For me when we specify a path we want that this path has a high priority, and
>not low priority.
But you are not always the end user. So, if a user puts
> Hi all,
>
> quite a big chance I am doing something wrong again, but here is my
> question:
> when building KDElibs with Visual C++ 2005 Express all goes well until
> building kdecore, especially kapplication.cpp.
> There, the following error occurs:
>
> D:\source\kde-svn\kdelibs\kdecore\klocal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
quite a big chance I am doing something wrong again, but here is my
question:
when building KDElibs with Visual C++ 2005 Express all goes well until
building kdecore, especially kapplication.cpp.
There, the following error occurs:
D:\source\k
Alexander Neundorf wrote:
>Hi,
>
>I just successfully compiled kdelibs/ from trunk with "make -j4" on my
> single processor machine.
>Could you please verify that it also works for your setups ?
>If there are problems, let me know.
I tried a make -j25 on the compile farm here at Trolltech and sudd
Brad King wrote:
>You're probably right. I've never encountered the problem because I use
>CMake for everything. It automatically pulls in library dependencies
>and links the executable explicitly to all libraries (at least if the
>project providing the libs uses export_library_dependencies prope
Hi
I will give you the whole set of commands we are currently performing to
"compile" the ocaml-file. OCaml is very c-like...
ocamldep -I +facile *.mli *.ml > .depend
ocamlc -I +facile -c chemset.mli
ocamlopt -I +facile -c chemset.ml
ocamlc -I +facile -c parser.mli
ocamlopt -I +facile -c parser
47 matches
Mail list logo
