[CMake] unit tests include in "all" but not install

Scott Aron Bloom scott at towel42.com
Sat Mar 21 10:14:46 EDT 2015


And here is the ironic part..

Make test, does NOT have a dependency to build all the tests...

YET, make install does :(

Personally, I want it the other way around, where make test, at least has each tests executable as a dependency, and makes sure they are not out of date before run...

But make install, should just build the things being installed and THEIR dependencies, NOT the ALL dependency.

Scott
From: CMake [mailto:cmake-bounces at cmake.org] On Behalf Of Scott Aron Bloom
Sent: Saturday, March 21, 2015 7:07 AM
To: David Cole; Nils Gladitz
Cc: CMake ML
Subject: Re: [CMake] unit tests include in "all" but not install

I run make test separately ..   I just don't want it to go through the dependency check for thr 600 unit tests..


--Scott
-------- Original message --------
From: David Cole <DLRdave at aol.com<mailto:DLRdave at aol.com>>
Date:03/21/2015 04:19 (GMT-08:00)
To: Nils Gladitz <nilsgladitz at gmail.com<mailto:nilsgladitz at gmail.com>>
Cc: Scott Aron Bloom <scott at towel42.com<mailto:scott at towel42.com>>, CMake ML <cmake at cmake.org<mailto:cmake at cmake.org>>
Subject: Re: [CMake] unit tests include in "all" but not install

"In general, I want all my unit tests to be built when I do a make
all, but I really don't care if they are up to date for a make
install."

Are you sure you don't care? If your unit tests are out-of-date with
respect to what you are installing, and you have not run them against
what you are installing .... then how do you have confidence that what
you are installing is acceptable?

Just sayin'...



On Sat, Mar 21, 2015 at 3:23 AM, Nils Gladitz <nilsgladitz at gmail.com<mailto:nilsgladitz at gmail.com>> wrote:
> On 21.03.2015 00:23, Scott Aron Bloom wrote:
>
> For those who couldn't understand my jibberish.. I apologize, never send
> email from a phone...
>
>
>
> Ill restate...
>
>
>
> In general, I want all my unit tests to be built when I do a make all, but I
> really don't care if they are up to date for a make install.
>
>
>
> Is that a possibility?  Ie, add the exclude from all attribute, that is
> really an exclude from install?
>
>
> You can remove the "all" dependency from "install" with:
>
> http://www.cmake.org/cmake/help/v3.2/variable/CMAKE_SKIP_INSTALL_ALL_DEPENDENCY.html
>
> But I don't think there is anything to add dependencies back to the
> "install" target.
>
> Nils
>
> --
>
> Powered by www.kitware.com<http://www.kitware.com>
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20150321/c4c336c2/attachment.html>


More information about the CMake mailing list