> If you want native executables, you can specify it in the CMakeLists for each > target > or set the option CMAKE_OCaml_NATIVE to TRUE.
Thanks for your clarification. > If you mean .mli files, hopefully they are managed. I would prefer to map the file name for the OCaml interface compiler also to a CMake cache variable. >> librarian (linker?) > You can use the CMake GUI to change the variables CMAKE_OCaml_LINKER_FLAGS*. I would prefer to map the file name for the OCaml archive generator also to another CMake cache variable. How do you think about to distinguish this program from other linking tools? >> Would further checks be useful for tools like "as" (GNU assembler), "ar" and > "ranlib" from the software package "binutils"? > [...] Do you have an example where it is necessary ? The software component "flexlink" (from "ocamlopt") depends on these tools. http://alain.frisch.fr/flexdll.html#internals How do you think about the addition of commands like "add_OCaml_executable" and "add_OCaml_library"? Do the additions from your CMake module work together with the command "install(TARGETS ...)"? Regards, Markus -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
