[CMake] Best practice for configuration-dependent defaults?

2018-08-17 Thread Sam Edwards
Hi all! I have a project with some options that have different defaults depending on the configuration used to build the project. For example, support for a certain (easy to support, but relatively uncommon) file format should be on by default, except when building in the MinSizeRel configuration.

Re: [CMake] Why does CMake 3.9.0 open VS2017 when targeting 2013 after installing 2017... sigh.

2018-08-17 Thread Brian Davis
> > Can't that be set by passing the toolset with a -T > > That is what I was trying to say with my last sentence. You will need > to use CMake 3.12 to have support for specifying the minor toolset > version though. > > >>> > >>> The MSVC / CUDA support recently has been very challenging to kee

Re: [CMake] Expected behaviour of #cmakedefine

2018-08-17 Thread Ian Cullen
Agreed, version numbers will never not be set so #define is the better choice in this case. However this seems like an easy thing for users to trip-up on, particularly as only #cmakedefine is used in the configure_file() manual page. Perhaps an additional example, or an INFO/WARNING section in