On Mon, Dec 1, 2008 at 12:25 PM, cyril_wobow <[EMAIL PROTECTED]> wrote:
> Robert Dailey a écrit : > >> That is indeed how I would expect it to work, but that's not what is >> happening. Below is the actual CMake code I'm using to generate projects: >> >> <snip> >> >> Inside of another CMakeLists.txt file in a different subdirectory, I'll >> call *library_component( ProjectName )*. Is this a bug in CMake or am I just >> doing this incorrectly? Help would be appreciated! Thank you. > > I remember an issue (still pending) where the PROJECT() macro would have to > be invoked from within the root CMakeList file. This problem occured to me > while writing my homemade macros and I had to work it around by splitting > my macro in half and having the following in my root CMakeList file : > MYMACRO1(...) > PROJECT(xxx) > MYMACRO2(...) > ... which is ugly and could really use a fix. That's going to be obnoxious if that is indeed the case. Was the problem you were experiencing anything like mine?
_______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
