2010/7/5 John Drescher dresche...@gmail.com
I see, thanks. I intend to write a Python script that adds the extra
platform solution, because we really need that. Visual Studio and
Code::Blocks project files are XML files, so it shouldn't be too hard.
What is wrong with different build
On 26 August 2010 10:17, Mark Van Peteghem mar...@gmail.com wrote:
We do have different build folders for each compiler / ide, but I mean
'build folder' as the folder where the object files and executable ends. We
just want one project file with different platform solutions, so we don't
have
On Mon, Jul 05, 2010 at 01:31:41PM +0200, Mark Van Peteghem wrote:
I see, thanks. I intend to write a Python script that adds the extra
platform solution, because we really need that. Visual Studio and
Code::Blocks project files are XML files, so it shouldn't be too hard.
If possible, I would
On Mon, Jul 05, 2010 at 10:47:32AM -0400, John Drescher wrote:
What is wrong with different build folders for each compiler / ide?
I'm interested in an answer to this question as well.
For me, the biggest thing is that it's what VS developers are accustomed
to. I've been educating it out of
] *On
Behalf Of *Mark Van Peteghem
*Sent:* Thursday, July 01, 2010 2:13 AM
*To:* cmake@cmake.org
*Subject:* Re: [CMake] Different configurations with Visual Studio
Thanks, this works. Actually
if(CMAKE_CONFIGURATION_TYPES)
set(CMAKE_CONFIGURATION_TYPES Debug Release DebugMX31 ReleaseMX31
I see, thanks. I intend to write a Python script that adds the extra
platform solution, because we really need that. Visual Studio and
Code::Blocks project files are XML files, so it shouldn't be too hard.
What is wrong with different build folders for each compiler / ide?
John
-boun...@cmake.org] On Behalf
Of Mark Van Peteghem
Sent: Thursday, July 01, 2010 2:13 AM
To: cmake@cmake.org
Subject: Re: [CMake] Different configurations with Visual Studio
Thanks, this works. Actually
if(CMAKE_CONFIGURATION_TYPES)
set(CMAKE_CONFIGURATION_TYPES Debug Release DebugMX31
Thanks, this works. Actually
if(CMAKE_CONFIGURATION_TYPES)
set(CMAKE_CONFIGURATION_TYPES Debug Release DebugMX31 ReleaseMX31)
set(CMAKE_CONFIGURATION_TYPES ${CMAKE_CONFIGURATION_TYPES} CACHE STRING
Reset the configurations to what we need FORCE)
endif()
also works for me. I've added
I found another problem with CMAKE_CONFIGURATION_TYPES, it doesn't work with
Code::Blocks, even though you can have different configurations in
Code::Blocks. Is there a way to make this work for Code::Blocks, or is it
not yet implemented?
--
Mark
___
Hi,
I am using CMake to generate Visual Studio project files, later also for
CodeBlocks.
It seems that CMake generates four different configurations for Visual
Studio: Debug, Release, MinSizeRel and RelWithDebInfo. However, I need other
configuations, Debug and Release, both for Win32 and MX3,
On 28. Jun, 2010, at 15:17 , Mark Van Peteghem wrote:
Hi,
I am using CMake to generate Visual Studio project files, later also for
CodeBlocks.
It seems that CMake generates four different configurations for Visual
Studio: Debug, Release, MinSizeRel and RelWithDebInfo. However, I need
11 matches
Mail list logo
