On 01/13/2017 11:45 AM, Shmuel H, wrote:
> * From the other side, programmers should be able to use a script
> language to customize their build process.
>
> For example, a simple declaration (pseudo code):
> cmake_libraries += {
> ["name": "myLib",
> "files": "myLib.c",
> "link_type": "static"]
> }
The declarative part needs to be self-standing so that it can be loaded
by an IDE, edited by the user, and saved back out in the original format
with a minimal diff. An IDE will have no idea how to write snippets back
into a procedural script. This is one reason CMakeLists.txt files cannot
be edited through an IDE except as text files.
My proposal is that the declarative part would have most of the build,
but with some kind of named condition/config variables. Then the
procedural part will introspect the system to determine the values of
the configuration variables so that CMake can evaluate the conditions.
-Brad
--
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://public.kitware.com/mailman/listinfo/cmake-developers
