[CMake] Global build target for global post-build stage ?

[David Cole]

What's the motivation behind your question?

(1) Do you want to do this custom command at the end of *every* developer's
*every* call to make from your top level?
(2) Or do you want to post an automatic build from a build machine when the
build is 'done'...?
(3) Something else?

For (2), I'd recommend using a ctest -S script to drive dashboard builds of
your project. Then you could add a test that does what you want or you could
add a step to your dashboard script that happens after the build stage is
over...

For (1) or (3) we'll have to think some more...

:-)
David


On 12/6/06, Eric BOIX <eboix at ens-lyon.fr> wrote:
>
>         Dear David Cole,
>
> Quoting David Cole <david.cole at kitware.com>:
> > You could add a custom target that depends on all the other targets in
> your
> > project.
> True enough. But for big projects this places a global constraint on all
> CMakeLists.txt maintainers who get to update the custom global target
> dependencies each time they add/delete a new target. One could resolve
> to some hierarchy of targets instead of a flat approach. Still this
> sounds heavy and fragile (since it depends on each maintainer). Doesn't it
> ?
>
> For our project we build 30 sub-libraries or libraries (I know this is
> probably a poor design, nevertheless...), 34 independent binaries (which
> is reasonable), a user's and programmers guide, the doxygen documentation
> not to mention de Ctest part.... The custom global target would be quite
> complicated. And to that the fact that some targets are only build when
> some OPTION flags are set...and things get quickly out of control.
>
>         Thanks anyhow !
>         Yours,
>         Eric Boix.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/cmake/attachments/20061206/71b0503f/attachment-0001.htm