[CMake] Announcing CMake BASIS, a set of CMake based project interoperability and automation tools

[Andreas Schuh]

On Jan 23, 2014, at 1:11 PM, Andreas Schuh <andreas.schuh.84 at gmail.com> wrote:

> 
> On Jan 23, 2014, at 9:40 AM, Stephen Kelly <steveire at gmail.com> wrote:
>> 
>>>> Another example: You have code for adding scripts as executables. What
>>>> are the generic (non-BASIS related) use cases for that?
>>>> 
>>> You can define dependencies among them or to modules written in the same
>>> scripting language. 
>> 
>> Can you say why this is useful? 

Let me give just one more example, if you could define that a script depends on another executable target (e.g., build from C++), when I rebuild only the script, the other executable will be recompiled and linked if it has changed since the last build as well. This is not possible at the moment without custom build commands/targets, but often (Shell) scripts are indeed calling other executables of your package. Then if you just want to test the changes made to the script, you can simply run “make myscript” and all dependencies will be updated as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20140123/4bdda47b/attachment.html>