Hello again,
I'm wondering what the best way to going about producing make files and
visual studio files at the same time is. I want to use nmake to build
my tree, but want visual studio project files so that the developers can
continue to with within the visual studio environment, which would ca
Josef Karthauser <> wrote:
> Hello again,
>
> I'm wondering what the best way to going about producing make files
> and visual studio files at the same time is. I want to use nmake to
> build my tree, but want visual studio project files so that the
> developers can continue to with within the vi
Josef Karthauser a écrit :
Hello again,
I'm wondering what the best way to going about producing make files and
visual studio files at the same time is. I want to use nmake to build
my tree, but want visual studio project files so that the developers can
continue to with within the visual stu
> -Original Message-
> From: Torsten Martinsen [mailto:[EMAIL PROTECTED]
> Sent: 01 October 2007 14:43
> To: Josef Karthauser; Cmake Mailing List
> Subject: RE: [CMake] Building both make files and visual studio files.
>
> Josef Karthauser <> wrote:
>
Alas I don't think that that is going to be flexible enough. In order
to do that we would need more flexibility within cmake for the
generation of the vcproj files, as it only knows about conventional
builds. For example Xbox360 builds don't have a VCCLCompilerTool,
instead having a
VCCL
To address this issue I had to patch the cmake source files like this:
if(this->PlatformName == "XBox 360")
{
aCompilerTool = "VCCLX360CompilerTool";
}
else
{
aCompilerTool = "VCCLCompilerTool";
}
How do you go about setting the platformname from within the CMakeLists.txt? I
had a look at the code, but concluded that it wasn't configurable. Is that
another local hack?
Actually in the global generator we added a "RealPlatformName" AND a
"Platform" members.
We pass a custom "PLATFORM
