On Friday 17 August 2007 10:07, Pau Garcia i Quiles wrote: > Quoting Alexander Neundorf <[EMAIL PROTECTED]>: ... > > Do you mean the project templates for cmake projects which come with > > KDevelop ? > > I didn't look after them for a long time... > > Yes, those templates.
Ok, I'll have a look. > >> I removed the CMakeFiles directory and the Makefile KDevelop creates > >> and used my own stuff: > >> 1. Create a "build" directory in your project's directory > >> 2. Use this Makefile: > >> > >> ======== > >> all: > >> cd build; cmake ..; make > >> > >> elampodaemon.wt: all > >> > >> clean: > >> rm -rf build/* > >> ======== > >> (replace "elampodaemon.wt" with your target) > > > > There is no need for that. > > You can just create a buildtree wherever you like and run cmake there: > > src/$ mkdir build > > src/$ cd build > > src/build/$ cmake -GKDevelop3 .. > > ... > > > > and project files cmake generates will work as expected. > > Yes, but the Makefile I'm using allows you to do everything in > KDevelop, no need to go to the command line. With my approach too, it's only the first time when you initially run cmake to generate the makefiles/project files. > I am not using CMake-generated KDevelop project files, though. > > Even more, using DCOP it should be possible to close and reopen the > project once CMake generates a new .kdevelop file just like CMake did > in Visual Studio: > dcop kdevelop-5898 KDevProject closeProject > dcop kdevelop-5898 KDevCore openProject > /home/pgquiles/personal/escarlampio/elampo/elampo.kdevelop Interesting idea. OTOH this is quite slow in KDevelop. Bye Alex _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
