[cmake-developers] EXCLUDE_FROM_DEFAULT_BUILD testing

Petr Kmoch petr.kmoch at gmail.com
Wed Oct 17 03:24:36 EDT 2012


On Tue, Oct 16, 2012 at 5:26 PM, Brad King <brad.king at kitware.com> wrote:

> On 10/16/2012 11:04 AM, Brad King wrote:
> > I tested it locally on VS 6, 7.1, 8, 9, 10, and 11 all with
> > spaces in the path.  I need to investigate the failures on
> > the dashboard to identify the problem.
>
> Since we're trying to keep the dashboard as clean as possible
> right now (to more directly test any changes meant to fix any
> regressions in 2.8.10-rc1) I'm reverting the change:
>
>  http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=69e305f2
>
> until after the final 2.8.10 release and when we've resolved
> these failures.  We can restore the topic later.
>

OK, I understand release candidate mode is not the time to add new features
:-)


>
> The problem is that MSBuild may be used as the build tool
> instead of devenv, especially for VS Express editions.  The
> MSBuild tool doesn't even read the .sln so this property does
> not make sense.  One option is to run the test only when the
> build tool is devenv.
>

I'm a bit confused. We occasionally use MSBuild for driving builds at work,
but we always feed it solution files. How do you run it so that it doesn't
read them? And how does it then cope with project dependencies etc.?

Anyway, the test only makes sense in cases where the property applies, so
if MSBuild doesn't honour the build/don't build settings in the .sln,
there's no point in running it with MSBuild.

Petr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20121017/9e531baf/attachment.html>


More information about the cmake-developers mailing list