Hi, Why not just use C/C++ for writing build system (bs) rules? C++ is for those who have modern compilers. (By C++ I mean modern C++11-14-17). C is for everything. These two apis can coexist.
CMake first will build bs itself (e.g. into shared library) and then load and execute it on the source tree. I'll investigate this in my C++ Archive Network [1] project very soon. Now I have mentioned here declarative (YAML) syntax with custom CMake insertions. For example, see specifications [2-5]. [1] https://cppan.org/ [2] https://cppan.org/pvt.cppan.demo.sqlite3/version/3.16.1/specification [3] https://cppan.org/pvt.cppan.demo.unicode.icu.i18n/version/58.2.0/specification [4] https://cppan.org/pvt.cppan.demo.webp/version/0.5.1/specification [5] https://cppan.org/pvt.cppan.demo.boost.conversion/version/1.62.0/specification On 13 January 2017 at 18:56, Brad King <brad.k...@kitware.com> wrote: > On 01/12/2017 01:20 PM, Shmuel H, wrote: >> maybe a general problem with dependencies, which generally >> make our life harder? > > Yes. People typically install CMake only in order to build something else. > If Python were added as an external dependency then that would be yet > another step. If it were bundled then our bootstrap script and CMake-based > build of CMake itself would both have to learn to build Python. Python > is also a distribution in addition to a language, so deploying it raises > the question of what to bundle with it. None of these is something I'd > like to have added to the responsibilities of maintaining and distributing > CMake. > > There are already other build systems that use Python as their language, > but many people still choose CMake over them anyway. > >> However, for me - a user, a known and well-designed programming language >> for CMake would be very helpful. I can't say that for every other user, >> but I think it would make their life a lot easier too. > > As Charles Huet mentioned Lua is a good choice because it provides a > language and is portable to everywhere that has C. It is also not a > distribution. I've posted in the past a design for a cmake_lua command > that allows one to use Lua code within CMakeLists.txt files. Actually > using it as a full replacement language though will first require more > refactoring internally as I mentioned in my previous post. > > As I've mentioned in previous discussions, if we're going to go through > a language change we should make sure it addresses important needs. > Having a declarative specification that can be externally tooled will > be helpful to IDEs. I'd envision such a format that is then imported > by the procedural-language part of the configuration process for > evaluation of conditions and finalization for the current target. > > Without a comprehensive design I'm hesitant to proceed on any such effort. > > -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 -- Egor Pugin -- 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
