Hi Ryan, I've started using your MSVCStaticRuntime.cmake and everything
worked well until I tested it with NMake Makefiles generator, that
doesn't use CMAKE_CONFIGURATION_TYPES, so I edited your file to add the
content of CMAKE_BUILD_TYPE to the SUFFIXES of list_combinations in
order to make the
Hi,
CMake creates a VS project file that uses the dynamic run-time for
static libs. This is not what I want in release builds.
How do I change this?
Greetings,
Olaf
cmake_minimum_required(VERSION 2.4)
set(CMAKE_BUILD_TYPE release)
include_directories(.)
add_library(
xbt
On 7/30/10 5:25 AM, Olaf van der Spek wrote:
Hi,
CMake creates a VS project file that uses the dynamic run-time for
static libs. This is not what I want in release builds.
How do I change this?
Greetings,
Olaf
cmake_minimum_required(VERSION 2.4)
set(CMAKE_BUILD_TYPE release)
On Fri, Jul 30, 2010 at 1:52 PM, Ryan Pavlik rpav...@iastate.edu wrote:
Almost nobody uses the static runtime unless someone else's lib forces them
Why not?
If Windows had proper package management I wouldn't use it either, but
until then...
Olaf
___
On 7/30/10 7:01 AM, Olaf van der Spek wrote:
On Fri, Jul 30, 2010 at 1:52 PM, Ryan Pavlikrpav...@iastate.edu wrote:
Almost nobody uses the static runtime unless someone else's lib forces them
Why not?
If Windows had proper package management I wouldn't use it either, but
until then...
Olaf
On Fri, Jul 30, 2010 at 2:11 PM, Ryan Pavlik rpav...@iastate.edu wrote:
On 7/30/10 7:01 AM, Olaf van der Spek wrote:
On Fri, Jul 30, 2010 at 1:52 PM, Ryan Pavlikrpav...@iastate.edu wrote:
Almost nobody uses the static runtime unless someone else's lib forces
them
Why not?
If Windows had
