[CMake] [VS gen] Multiple configurations code

David Cole david.cole at kitware.com
Tue Jul 27 07:26:19 EDT 2010

On Tue, Jul 27, 2010 at 5:45 AM, Verweij, Arjen <VerweijA at tass-safe.com>wrote:

> David,
> I hear what you are saying, but a lot of legacy Makefile based system
> support "make" and "make debug" alongside each other. I'm still looking for
> the cmake way to easily mark a small part of a project to be built with
> debug flags. For instance, if you have functionality in a static archive,
> you just link the new debug enabled object file against the main.o and the
> archive and you end up with some debugging symbols in no time.
> Regards,
> Arjen

Replicating that with CMake should be possible, too, but it's not the
typical everyday use case.

You can certainly do anything you want with custom commands, but it does not
make for easy portability to other OS'es and compilers when you start doing
things like that.

> From: cmake-bounces at cmake.org [mailto:cmake-bounces at cmake.org] On Behalf
> Of David Cole
> [snip]
> Since this is a prevalent scheme that is widely used by folks coming from
> single-config, single-architecture (makefile based) build systems... it's
> the way CMake has gotten to the point it's at now. I'm not saying this is
> good or bad, just explaining that this is the way it is, and that there are
> historical reasons why we got to this point.
> _______________________________________________
> Powered by www.kitware.com
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100727/cd187951/attachment.htm>

More information about the CMake mailing list