On Fri, Nov 7, 2008 at 6:34 PM, Neal Meyer wrote: > On Fri, Nov 7, 2008 at 12:31 PM, Miguel A. Figueroa-Villanueva > <[EMAIL PROTECTED]> wrote: >> >> On Fri, Nov 7, 2008 at 4:11 PM, Neal Meyer wrote: >> > On Friday 07 November 2008, Neal Meyer wrote: >> >> I've tried the existing generator in cmake on the Mac on my existing >> >> project but it generated a crazy MakeFile project that builds, but is >> >> really unorganized and doesn't really help any. I tried using the >> >> CMake >> >> project and discovered that the build directory structure I was using >> >> appears to be most of my problem. I had created a directory called >> >> build >> >> under the root of the cmake project then ran cmake with the working >> >> directory set to the build folder [cmake .. -G "Eclipse CDT4 - Unix >> >> Makefiles"] The project in eclipse was mostly unusable because the >> >> source >> >> and the files were all over the place. Once I ran cmake in the source >> >> file. It behaved much better. >> > >> > Please read that wiki page, it documents all the issues Eclipse has with >> > out-of-source builds. If there is something more, please let us know. >> > http://www.cmake.org/Wiki/Eclipse_CDT4_Generator >> > Thanks Alex. I'm playing with the generator on Windows and Mac, and now >> > that I understand the Eclipse limitation with the linked resource >> > directory >> > it makes it clearer. On my windows project I'm getting several linked >> > directories in the main project that seems like everything that has an >> > add_subdirectory in the root CMakeLists.txt file, but on my Mac project >> > I'm >> > just getting a single linked resource for the root of the entire source >> > tree. Is that expected? Both are using out of source build >> > directories. >> >> Hello Neal, >> >> Well, there is no intended difference between Mac and Windows. The >> linked resources are created for every "project()" call; not for the >> add_subdirectory. >> >> I'll appreciate your testing to refine the generator to work >> out-of-the-box in the Mac. >> >> --Miguel > > Thanks Miguel - that clears up the differences I'm seeing on the two > projects. One has a number of project calls init and the other only had a > single one at the top level. When I add project calls to the nested > directories they come out to the top level of the eclipse project. Will the > root always be left in the eclipse project then if I have a project() call > there? > > -Neal
Yes, if there is a project() call in the root CMakeLists.txt file, then the eclipse project should contain the linked_resource to the root dir. --Miguel _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
