On Feb 5, 2008 11:08 AM, Hendrik Sattler <[EMAIL PROTECTED]> wrote: > > Quoting Brandon Van Every <[EMAIL PROTECTED]>: > > On Feb 5, 2008 10:05 AM, John Spray <[EMAIL PROTECTED]> wrote: > >> > >> If I were invoking a second CMake, would I be able to make the host > >> CMake aware of the second as a dependency? > > > > Sure. add_custom_command, add_custom_target. The subsidiary CMake > > would have to actually output something. You'd have to know what that > > output is going to be, and how to invoke the build. > > Or a new command > add_indep_subdirectory() > which does automate that by forgetting about most cmake settings but targets. > Example: compiling a firmware code with a cross-compiler, then > converting that binary into a .c file and including that into a > binary: two compiler chains and one add_custom_command. > It would restrict to using a separate subdirectory for the different > toolchain (else it is probably not complex enough).
What's wrong with doing things the usual way? I'm not seeing a reason to hide the standard mechanisms for calling external tools. CMake can be an external tool, there's nothing wrong with that. Cheers, Brandon Van Every _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
