[cmake-developers] FW: FW: Initial Attempt at Green Hill MULTI IDE Generator Support

[Geoffrey Viola]

> Please base further work on commit a00be665.

Will do.

>I see you added use of CMAKE_BUILD_TYPE to pick which flags to use.  Does this IDE support only one configuration at a time?
>Or, are users supposed to be able to pick the config at build time?

The IDE supports only one configuration at a time. As far as I can tell, typical MULTI projects are monolithic embedded compiled code where flags are edited at a global level. I figured CMAKE_BUILD_TYPE kind of works similarly except it is a little more stream lined.


Geoffrey Viola
SOFTWARE ENGINEER
asirobots.com



-----Original Message-----
From: Brad King [mailto:brad.king at kitware.com]
Sent: Thursday, April 09, 2015 10:54 AM
To: Geoffrey Viola
Cc: cmake-developers at cmake.org
Subject: Re: FW: FW: [cmake-developers] Initial Attempt at Green Hill MULTI IDE Generator Support

On 04/09/2015 08:56 AM, Geoffrey Viola wrote:
> I rebased on ff7ecb92 to create the new attached patch.

Thanks.  I moved the cmLocalGenerator change out into its own commit and then squashed everything else in the original topic and this patch together.  I made a few minor tweaks and merged to 'next' for testing again:

 cmLocalGenerator: Constify some cmTarget and cmGeneratorTarget arguments
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=051d8be1

 Add a 'Green Hills MULTI' generator on Windows
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a00be665

Please base further work on commit a00be665.

I see you added use of CMAKE_BUILD_TYPE to pick which flags to use.  Does this IDE support only one configuration at a time?
Or, are users supposed to be able to pick the config at build time?

Thanks,
-Brad

This message contains confidential information and is intended only for the recipient. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.