"Please create a separate build directory and run 'cmake path_to_kdelibs [options]' there."

[Tanner Lovelace]

On 3/29/06, Kurt Pfeifle <k1pfeifle at gmx.net> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdelibs-print-source-build-dir.diff
Type: application/octet-stream
Size: 877 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-buildsystem/attachments/20060329/5f72c3f9/attachment.obj