Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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/src/kde40svn/trunk/KDE/kdelibs > > > > > > [EMAIL PROTECTED]:~/src/kde40svn/trunk/KDE/build/kdelibs> cmake > > > ../../kdelibs -- debug output for Kurt, remove ASAP again: insource -1- > > > \ srcdir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- \ > > > bindir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- > > > > And you really don't have a CMakeCache.txt > > in /home/kdev4/src/kde40svn/trunk/KDE/kdelibs ? > > I had it; timestamp 1 hour ago. Must have been regenerated even after > I had nuked the srcdir. Ok, that's the reason why cmake says /home/kdev4/src/kde40svn/trunk/KDE/kdelibs is the bindir. If a CMakeCache.txt exists, you cannot rerun cmake from another directory without deleting this file first. Bye Alex -- Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de Home: neundorf AT kde.org- http://www.kde.org alex AT neundorf.net - http://www.neundorf.net ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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/kde40svn/trunk/KDE/build/kdelibs> cmake > > ../../kdelibs -- debug output for Kurt, remove ASAP again: insource -1- \ > > srcdir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- \ > > bindir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- > > And you really don't have a CMakeCache.txt > in /home/kdev4/src/kde40svn/trunk/KDE/kdelibs ? I had it; timestamp 1 hour ago. Must have been regenerated even after I had nuked the srcdir. For tonight I have to give up again; and will likely not have time to revisit the issue within the next 2 weeks. (It seems to hit just me -- maybe it goes away meanwhile.) > Bye > Alex Thanks, Kurt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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/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 Kurt, remove ASAP again: insource -1- \ > srcdir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- \ > bindir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- > > kdelibs requires an out of source build. Please create a separate build > directory \ > and run 'cmake path_to_kdelibs [options]' there. > -- Configuring done How about one more thing: from the directory you are running cmake: ls ../../kdelibs -Bill ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 cmake string compare > functions. How long is the full path to your source and build trees? > Here's something you might try. Can you rename your build directory > something like kdelibs-build and rerun cmake? It should not make > a difference, but if the string compare function is getting confused > that should make it work. Indeed it didn't make a difference. But I forgot to consider one thing: I had been running a cmake from SVN (about 2 days old). And in the meanwhile I've read the mailing list advice to rather stay away from this, and instead use specifically recommended tarballs. I didn't follow the advice for now; instead I updated cmake to current CVS and built once more. This didnt make it work either... But perhaps it is a cmake bug in current CVS? I'll use the latest tarball now and try again. > It also might make sense to have the error message print out what it > thinks the source and attempted build directory are. Something like > the patch I have attached. I can add that to the CMakeLists.txt > file if that sounds like a good idea. Thanks for being another caring soul :-) Alex has already done so (see my last posting). > Cheers, > Tanner Cheers, Kurt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 Kurt, remove ASAP again: insource -1- \ > srcdir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- \ > bindir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- And you really don't have a CMakeCache.txt in /home/kdev4/src/kde40svn/trunk/KDE/kdelibs ? Bye Alex -- Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de Home: neundorf AT kde.org- http://www.kde.org alex AT neundorf.net - http://www.neundorf.net ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 build. Please create a separate build \ > >directory and run 'cmake path_to_kdelibs [options]' there. > > -- Configuring done > > > > I wasn't able to follow the list for any changes, so please bear with me if > > I missed some obvious buildchange announcement. > > > > But I'm definitely in (an even virgin) "out of source" build directory. The > > source dir is also freshly checked out (into another virgin directory). > > > > What could be causing this error? A mistake, where someone has erraneously > > committed generated cmake files into SVN? Or something I'm doing wrong on > > my part? > > Please update kdelibs/CMakeLists.txt, I inserted some debug output, so you > see > what cmake considers to be the sourcedir and the builddir. Oh, thanks. This is a very special, caring treatment which I normally do not deserve :-) (but maybe the people deserve this for whom I'm trying to "learn" cmake building so I can help them better in the future). > Maybe you find the problem yourself, otherwise please post the output here. > > (starts with: "debug output for Kurt") Here we go... [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/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 Kurt, remove ASAP again: insource -1- \ srcdir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- \ bindir: -/home/kdev4/src/kde40svn/trunk/KDE/kdelibs- kdelibs requires an out of source build. Please create a separate build directory \ and run 'cmake path_to_kdelibs [options]' there. -- Configuring done > Bye > Alex Cheers, Kurt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 build. Please create a separate build \ > >directory and run 'cmake path_to_kdelibs [options]' there. > > -- Configuring done > > > > I wasn't able to follow the list for any changes, so please bear with me if > > I missed some obvious buildchange announcement. > > > > But I'm definitely in (an even virgin) "out of source" build directory. The > > source dir is also freshly checked out (into another virgin directory). > > > > What could be causing this error? A mistake, where someone has erraneously > > committed generated cmake files into SVN? Or something I'm doing wrong on > > my part? > > > > Cheers, > > Kurt > > and after reading this mail again, i was completely off. is there a > source tree in your ~/KDE/build/kdelibs folder? No. Unless it hides itself very well. > Perhaps you need to just > "rm -rf *" in your ~/KDE/build/kdelibs folder and try again. I'm not > really sure what the problem is. I had nuked srcdir as well as builddir and re-created both (that's why I called them both "virgin"). > Sorry for the previous mail with completely wrong info. Heh. It happens :-) Thanks for caring at all. Cheers, Kurt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 'cmake path_to_kdelibs [options]' there. > -- Configuring done > > I wasn't able to follow the list for any changes, so please bear with me if > I missed some obvious buildchange announcement. > > But I'm definitely in (an even virgin) "out of source" build directory. The > source dir is also freshly checked out (into another virgin directory). > > What could be causing this error? A mistake, where someone has erraneously > committed generated cmake files into SVN? Or something I'm doing wrong on > my part? Please update kdelibs/CMakeLists.txt, I inserted some debug output, so you see what cmake considers to be the sourcedir and the builddir. Maybe you find the problem yourself, otherwise please post the output here. (starts with: "debug output for Kurt") Bye Alex -- Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de Home: neundorf AT kde.org- http://www.kde.org alex AT neundorf.net - http://www.neundorf.net ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 your source and build trees? Here's something you might try. Can you rename your build directory something like kdelibs-build and rerun cmake? It should not make a difference, but if the string compare function is getting confused that should make it work. It also might make sense to have the error message print out what it thinks the source and attempted build directory are. Something like the patch I have attached. I can add that to the CMakeLists.txt file if that sounds like a good idea. Cheers, Tanner -- Tanner Lovelace clubjuggler at gmail dot com http://wtl.wayfarer.org/ (fieldless) In fess two roundels in pale, a billet fesswise and an increscent, all sable. kdelibs-print-source-build-dir.diff Description: Binary data ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 out of source build. Please create a separate build \ > >directory and run 'cmake path_to_kdelibs [options]' there. > > -- Configuring done > > > > I wasn't able to follow the list for any changes, so please bear with me if > > I missed some obvious buildchange announcement. > > > > But I'm definitely in (an even virgin) "out of source" build directory. The > > source dir is also freshly checked out (into another virgin directory). > > > > What could be causing this error? A mistake, where someone has erraneously > > committed generated cmake files into SVN? Or something I'm doing wrong on > > my part? > > > > Cheers, > > Kurt > > kdelibs requires a srcdir != builddir configuration now. this means > you'll need to create a seperate directory to compile kdelibs in, > something like the following will work > > cd /path/to/kdelibs > mkdir build > cd build > cmake .. > make > etc. > > hope this helps No. If you look at what I wrote, that *IS* what I'm doing.:-) (And I never did any different since the last 3 years.) My "cmake path_to_kdelibs" uses a relative path though -- could that be an issue? > -- > Matt Cheers, Kurt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 and run 'cmake path_to_kdelibs [options]' there. > -- Configuring done > > I wasn't able to follow the list for any changes, so please bear with me if > I missed some obvious buildchange announcement. > > But I'm definitely in (an even virgin) "out of source" build directory. The > source dir is also freshly checked out (into another virgin directory). > > What could be causing this error? A mistake, where someone has erraneously > committed generated cmake files into SVN? Or something I'm doing wrong on > my part? > > Cheers, > Kurt and after reading this mail again, i was completely off. is there a source tree in your ~/KDE/build/kdelibs folder? Perhaps you need to just "rm -rf *" in your ~/KDE/build/kdelibs folder and try again. I'm not really sure what the problem is. Sorry for the previous mail with completely wrong info. -- Matt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: "Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."
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 and run 'cmake path_to_kdelibs [options]' there. > -- Configuring done > > I wasn't able to follow the list for any changes, so please bear with me if > I missed some obvious buildchange announcement. > > But I'm definitely in (an even virgin) "out of source" build directory. The > source dir is also freshly checked out (into another virgin directory). > > What could be causing this error? A mistake, where someone has erraneously > committed generated cmake files into SVN? Or something I'm doing wrong on > my part? > > Cheers, > Kurt kdelibs requires a srcdir != builddir configuration now. this means you'll need to create a seperate directory to compile kdelibs in, something like the following will work cd /path/to/kdelibs mkdir build cd build cmake .. make etc. hope this helps -- Matt ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
