RE: Build problems with cmake / msvc2005
Hi, On 3/17/06, Michael Drüing [EMAIL PROTECTED] wrote: Hi, - cmake -GNMake Makefiles ..\kdelibs failed. It couldn't find the kdewin32 lib. The problem was, that it looked for a lib called kdewin32.lib, while by default the debug version is built which is called kdewin32d.lib. I have the same problem. However I built both the Debug and RelWithDebInfo builds, so I definitely have both kdewin32.lib and kdewin32d.lib (and corersponding *.dll's) Still CMakeSetup for kdelibs/ tells me You need to build kdewin32 first. The libs are right there under it's nose, it just needs to look inside win/ ;-) Any ideas? I used this batch file to set the correct paths inside a VS 2005 command prompt @echo off set OLDPATH=%PATH% set QTDIR=C:\Programme\qt- win-opensource-src-4.1.1 set CMAKE_DIR=C:\Programme\Develop\CMake set PATH=%OLDPATH%;%QTDIR%\bin;%CMAKE_DIR%\bin;C:\Programme\gnuwin32\bin;C:\Prog ramme\kdewin32\bin A make install in kdelibs/win will install the files to C:\Programme\kdewin32 (resp. C:\Program Files\kdewin32) by default. If you chose another path, adapt it accordingly. This is what I tried first, i.e. setting the PATH to include d:\kde4\bin (where I want kde). I even set %LIBPATH% to include d:\kde4\lib, both without success. I don't find anything helpful in the cmake logfiles but it seems that cmake searches for the lib files only in c:\program files\kdewin32 and not in $BUILDDIR/win (see findkdewin32.cmake). This did work correctly some time ago, so I guess it's a regression. CMake should at least also search in $BUILDDIR/win --Michael ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
RE: Build problems with cmake / msvc2005
Von: Michael Drüing [EMAIL PROTECTED]
snip
Okay, but then it should not only search in C:\Program Files\kdewin32 but
also in $KDEDIR/lib, because I don't want my kde installed in c:\program
files\kdewin32. I have set KDEDIR=d:\kde4 but CMake seems to ignore this.
Or
is there any other environment variable which I could set so that CMake
finds my kde4 installation path?
After copying the libraries to c:\program files\kdewin32, I get similar
problems with the other libraries, like libz.lib. They seem to be expected
in c:\program files\gnuwin32 or something. I have them in
d:\devel\local\{lib,include}, which are in the default MSVC search paths
defined by $LIB and $INCLUDE. These directories should also be searched
for
required libraries. Or maybe I'm missing something and there's already
some
env.variable which I can set to tell CMake where additional libraries can
be
found?
kdewin32.lib is independend from kde and should handled like any oher
external lib.
Maybe you're looking for CMAKE_LIBRARY_PATH / CMAKE_INCLUDE_PATH?
And when you've set GNUWIN32_DIR in cmakesetup to your location, it also
should find all other external libs too.
Christian
--
Feel free mit GMX FreeMail!
Monat für Monat 10 FreeSMS inklusive! http://www.gmx.net
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Build problems with cmake / msvc2005
Michael Biebl schrieb: Why do these problems raise up once more? What's the problem to build install kdewin32 *before* starting with kdelibs4? My problem was not to type make make install for kdewin32. I usually read the installation instruction and they clearly said so. The problem I had was, that FindKDEWin32.cmake looks for the library kdewin32.lib while by default the debug version is built and installed. So either the documentation should be updated, that kdelibs/win should be built with Release or RelWithDebInfo or FindKDEWin32 should look for kdewin32.lib and kdewin32d.lib I had to change this to avoid using debug kdewin32 with kdelibs which could lead to crashes. So yes, the documentation should be updated. Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
RE: Build problems with cmake / msvc2005
Why do these problems raise up once more? What's the problem to build install kdewin32 *before* starting with kdelibs4? We should move kdewin to antoher place asap to not bring up this discussion every month... nay ideas? kdesupport? Sorry to beat a dead horse, I didn't realize this was a recurring topic. It's not a huge problem, it's just, to paraphrase William, an additional bit of complexity that's not there on Unices. If it's going to be in kdelibs/, why not have it handled like every other subdirectory? On the other hand, if it's not going to be handled like every other subdirectory, why have it in kdelibs/? FWIW, my vote is to put the issue at rest indefinitely, one way or the other. Moving kdewin32 to kdesupport seems like a natural choice. ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Build problems with cmake / msvc2005
First off, we (Kitware) really need to get a new version of cmake out for kde. :) We are working on that. At 05:08 PM 3/16/2006, Michael Biebl wrote: Hi, I followed the instructions on http://www.kdelibs.com and tried to build the lateest qt-4.1.1, cmake and kdelibs. My experiences so far: - Building qt-4.1.1 with the supplied patch and msvc2005 was simple. - Compiling cmake: I downloaded cmake-2.2 and generated NMake Makefiles. Compiled and installed fine, but msvcp80.dll/msvcr80.dll were missing and not installed, so running cmake failed. This has been fixed in cvs cmake, vs 8 now requires manifests be embedded in executables. So, if you build cmake with cmake-2-2 it will not do that. If you did not install it would work, because the manifest files would be right next to the .exe files. So, for now the best thing would be to not install cmake, but use it out of the build tree. -Bill ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Build problems with cmake / msvc2005
Michael Biebl wrote: If I tried to generate the Visual Studio Project files with the latest cmake CVS snapshot, the Install Project did not work. It looked for the binary cmake in bin/cmake while it was generated in bin/release/cmake. I just found where/when this bug was introduced. I'll have it fixed by tomorrow morning. -Brad ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
