Hi!
2012/8/23 Daniel Pfeifer dan...@pfeifer-mail.de:
2012/8/22 Yury G. Kudryashov urkud.ur...@gmail.com:
Any latest install strategy is bound to generate subtle problems.
Dependencies among export sets should be explicit:
install(EXPORT MyExport DEPENDS YourExport)
How should I choose
Here an example how a Lua based build system could look like:
https://github.com/deplinenoise/tundra/blob/master/tundra.lua
And more details here:
http://deplinenoise.files.wordpress.com/2011/04/tundra43.pdf
Peter
--
Powered by www.kitware.com
Visit other Kitware open-source projects
On 22.08.2012 15:13, Brad King wrote:
On 08/22/2012 09:09 AM, Peter Kümmel wrote:
I wouldn't introduce a variable which will become obsolete, because
of the backward compatibility matra such a variable could never be removed.
Why not simply document that SYMBOL_OUTPUT_DIRECTORY is currently
On 08/22/2012 06:12 PM, Stephen Kelly wrote:
of linking there are multiple targets involved so we do not know
which one the user may mean.
I think it's something we can just define, is it not?
Some expressions might want the target being linked while others may
want the target in which the
On 08/23/2012 04:20 AM, Yury G. Kudryashov wrote:
Hi!
2012/8/23 Daniel Pfeifer dan...@pfeifer-mail.de:
2012/8/22 Yury G. Kudryashov urkud.ur...@gmail.com:
Any latest install strategy is bound to generate subtle problems.
Dependencies among export sets should be explicit:
install(EXPORT
On Thursday 23 August 2012, Peter Kümmel wrote:
Here an example how a Lua based build system could look like:
https://github.com/deplinenoise/tundra/blob/master/tundra.lua
And more details here:
http://deplinenoise.files.wordpress.com/2011/04/tundra43.pdf
So, another buildsystem
