Lloyd Hilaiel wrote:
step 0. use/advocate cmake for a year
step 1. read code, hack on code, get idea
me -> step 2. see if folks are interested/viable idea/makes sense
step 3. read code and make a concretish proposition
you -> step 4. get work done.
Are
step 0. use/advocate cmake for a year
step 1. read code, hack on code, get idea
me -> step 2. see if folks are interested/viable idea/makes sense
step 3. read code and make a concretish proposition
you -> step 4. get work done.
> Are you personally offering to do a goo
Lloyd Hilaiel wrote:
All I'm suggesting is that if a library were built as part of the cmake
build that drew a nice line between language parsing and makefile
generation, then people like me who constantly want to hack stuff up
and try stuff out would be able to do so at a level higher than cmak
To clarify, I'm not proposing the existing cmake language be
disbanded or thrown away. I think cmake is a compelling and complete
piece of software as it is, and perhaps a majority of the (existing)
users would not be interested in writing build scripts in another
language.
All I'm suggesting is
> The more and more I work with cmake, the more it feels like there are two
> (or more) distinct tools rolled into one...
>
> the "front end" is a piece of software that interprets CMakeLists.txt
> files,
> and drives a "back end". The back end is the stuff that actually
> generates
> compiler sp
Filipe Sousa wrote:
I remember someone suggesting Lua as a second language
http://public.kitware.com/pipermail/cmake-promote/2005-December/39.html
Just to add more baking soda to that fire, one thing that the CMake
language has that others don't, is an anal retentive IF(CONDITION) .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lloyd Hilaiel wrote:
> (probably off topic)
>
> The more and more I work with cmake, the more it feels like there are two
> (or more) distinct tools rolled into one...
>
> the "front end" is a piece of software that interprets CMakeLists.txt files,
>
Lloyd Hilaiel wrote:
(probably off topic)
The more and more I work with cmake, the more it feels like there are two
(or more) distinct tools rolled into one...
the "front end" is a piece of software that interprets CMakeLists.txt files,
and drives a "back end". The back end is the stuff that a
(probably off topic)
The more and more I work with cmake, the more it feels like there are two
(or more) distinct tools rolled into one...
the "front end" is a piece of software that interprets CMakeLists.txt files,
and drives a "back end". The back end is the stuff that actually generates
compi