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
how to debug it ?
Hi, I am this error: The end of a CMakeLists file was reached with an IF statement that was not closed properly. Within the directory: kde-4.0/kde4/cmake/snapshot/kdeaccessibility The arguments are: NOT CMAKE_INSTALL_PREFIX how to find CMakeLists.txt where there is this error ? Regards ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: how to debug it ?
Laurent Montel wrote: Hi, I am this error: The end of a CMakeLists file was reached with an IF statement that was not closed properly. Within the directory: kde-4.0/kde4/cmake/snapshot/kdeaccessibility The arguments are: NOT CMAKE_INSTALL_PREFIX how to find CMakeLists.txt where there is this error ? If this is happening during installation then this is due to a bug in CMake which I fixed last night. It was just introduced a few days ago so this is only the case if you are using a recent CVS cmake. Just update to today's CVS cmake and re-run it on your tree to solve the problem. Meanwhile I'll look at fixing CMake to report which file has the problem. -Brad ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: how to debug it ?
On Friday 17 March 2006 16:05, Brad King wrote: Laurent Montel wrote: Hi, I am this error: The end of a CMakeLists file was reached with an IF statement that was not closed properly. Within the directory: kde-4.0/kde4/cmake/snapshot/kdeaccessibility The arguments are: NOT CMAKE_INSTALL_PREFIX how to find CMakeLists.txt where there is this error ? If this is happening during installation then this is due to a bug in CMake which I fixed last night. It was just introduced a few days ago so this is only the case if you are using a recent CVS cmake. Just update to today's CVS cmake and re-run it on your tree to solve the problem. Meanwhile I'll look at fixing CMake to report which file has the problem. Ok thanks. I will update it. Do you think to release a new cmake tarball ? Regards ___ 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: Other pb with cmake
On Friday 17 March 2006 18:17, Laurent Montel wrote: On Friday 17 March 2006 17:28, Alexander Neundorf wrote: ... In order for the preprocessor to find build/lib/board.moc, build/lib/ would have to be added to the include path, just as build/ is part of the include path. This would mean *both* directories would be in the include path and for both files, src/board.cpp and src/lib/board.cpp the include path would be the same, so for both source files the *same* board.moc would be found first, so both would include build/board.moc. So I think we really have to change the moc handling for these conflicting files, i.e. automoc for on of them, and manual moc for the others, like this: set_source_files_properties(src/lib/board.cpp ...more files PROPERTIES SKIP_AUTOMOC TRUE) qt4_wrap_cpp(MY_SRCS src/lib/board.h ...more files which need to be mocced) Where is the difference ? we will generate .moc too. we will link with src/lib/board.moc and src/board.moc But the command line has to include -Ibuild/ -Ibuild/lib/, and this for both files, and so the preprocessor will find the same board.moc for both source files. So how your method will fix potential problem ? It will generate a src/board.moc (which will be included) and a src/lib/moc_board.cxx (which will be compiled as a separate file). 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: 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
cmake: frameworks and bundles on OS X
Hi, there is currently being worked on support for frameworks and bundles on OS X : http://public.kitware.com/pipermail/cmake/2006-March/008667.html Maybe you want to comment on it, ideally on cmake@cmake.org ? 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: How to replace configure.in.bot ?
On Friday, 17. March 2006 19:09, Laurent Montel wrote: find_package(JPEG) if (JPEG_FOUND) add_subdirectory(foo) else (JPEG_FOUND) message(STATUS To compile foo install the JPEG library) endif (JPEG_FOUND) Ok I will use it. And its automatically guaranteed to run after everything else? (the .bot in configure.in.bot means bottom of execution order). -- Dirk//\ ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: How to replace configure.in.bot ?
On Friday 17 March 2006 21:17, Dirk Mueller wrote: On Friday, 17. March 2006 19:09, Laurent Montel wrote: find_package(JPEG) if (JPEG_FOUND) add_subdirectory(foo) else (JPEG_FOUND) message(STATUS To compile foo install the JPEG library) endif (JPEG_FOUND) Ok I will use it. And its automatically guaranteed to run after everything else? (the .bot in configure.in.bot means bottom of execution order). If it is intended to run after everything else, it should go to the end of the toplevel CMakeLists.txt. 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
what version of qt to use?
For the dashboards at kitware, I did this: download qt-x11-opensource-src-4.1.0/ Then, I applied some patch to: qsyntaxhighlighter.cpp But, now the dashboards have errors, and I was told to use qt-copy. Is there another small patch? What about windows? I don't think qt-copy will build on windows. Thanks. -Bill ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
New KDE CMake Release 2.3.4
I have created a new kde CMake release, it can be found here: http://www.cmake.org/files/v2.3/cmake-2.3.4-20060317-win32.exe http://www.cmake.org/files/v2.3/cmake-2.3.4-20060317.tar.gz You should be able to use the windows binary, and avoid having to build CMake on windows. I have also tagged the CMake repository with CMake-2-3-4-kde, if you want to use a cvs version of cmake, you can use that tag. The .tar.gz file is a unix line feed tar ball. The .exe is a windows installer. Please let me know if there are any issues. We are working on the official CMake 2.4 release, so please report bugs soon, so we can get the fixes into the official release. Thanks. -Bill ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: what version of qt to use?
William A. Hoffman schrieb: For the dashboards at kitware, I did this: download qt-x11-opensource-src-4.1.0/ Then, I applied some patch to: qsyntaxhighlighter.cpp But, now the dashboards have errors, and I was told to use qt-copy. Is there another small patch? What about windows? I don't think qt-copy will build on windows. The patches from qt-copy apply fine on qt/windows Christian signature.asc Description: OpenPGP digital signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
