[CMake] How to make sure "make test" depends on "make all"

Hugo Heden hugoheden at gmail.com
Wed Jun 24 09:01:10 EDT 2009


On Wed, Jun 24, 2009 at 2:08 PM, Shlomi Fish <shlomif at iglu.org.il> wrote:

> On Tuesday 23 June 2009 11:57:16 Hugo Heden wrote:
> > On Tue, Jun 23, 2009 at 9:56 AM, Shlomi Fish <shlomif at iglu.org.il>
> wrote:
> > > Hi all!
> > >
> > > I'm using cmake-2.6.4-3mdv2010.0 on Mandriva Linux Cooker, and ran into
> a
> > > problem. I want "make test" (which is a custom target) to depend on
> "make
> > > all", in this codebase:
> > >
> > >  <http://svn.berlios.de/svnroot/repos/fc-solve/trunk/fc-solve/source/>
> >
> > I can't say that I understand the error messages you're getting, but it
> is
> > unfortunately *not* possible to make built-in targets like "test", "all"
> > and "install" depend on each other. See for example this bug:
> >
> > http://public.kitware.com/Bug/view.php?id=8438
>
> Interesting. Is this a bug or a (mis-)feature? If I work on it and
> contribute
> a patch that will fix it, will it be accepted?
>
>
I think it is a "bug" (but I am just a user). See also one of the comments
in http://public.kitware.com/Bug/view.php?id=6348  -- I'll paste it here
(with some boldificiations that are purely mine -- I hope they don't screw
up the view too much for text-only viewers):

*Brad King:*

> What we really need is* a notion of a "local target"* that runs the same
> rule in every directory with that directory as the working directory. The
> rule would not be allowed to have any input or output files...just a command
> line to run unconditionally. On IDE generators the target would appear only
> once and always run in the top level. Currently the *"install", "test",
> and "clean" targets work like this*. It would have to *become a
> first-class feature*. I'd also want to convert the install, test, and
> clean targets to be defined this way in the first place. They could be
> created at the beginning of the configure step and *referencable by users*
> .
>
>
I am not sure whether this would mean that you can force "test" to depend on
"all" (which was your original concern), since "all" is not mentioned
above..? But forcing "test" to depend on "install" would work I guess.

/Hugo Heden
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20090624/031b1ec6/attachment-0001.htm>


More information about the CMake mailing list