Sorry if this has been asked many times before but here goes.
How can I configure Visual Studio 2005 (Professional Edition) to compile my
source using different toolchains? For example gcc for win32, cross gcc for
Linux etc.
I think I need to add a platform, but I don't know how to do this.
I've tried adding a platform in the configuration manager, but little else
seems to light up. Perhaps I should be using Eclipse .....
Regards,
Shed
Take a look at MSBuild to see if that helps.

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
> Sorry if this has been asked many times before but here goes.
>
[quoted text clipped - 12 lines]
>
> Shed
You have a few different options.
1) use a Makefile project. This is misnamed as it's really a command prompt
driven project where you define command lines for, BUILD, REBUILDALL, and
CLEAN. We do this for embedded platforms using GCC and Gnu make. The catch
is there is no direct support for a "project nor any compiler or build
settings. So you have to manually add files to your make when you want new
files added to your makefile build.
2) Create MSBuild Targets to support building your GNU code as a build
project (eliminating the use of Gnu Make)
3) Create a VSIP project package that supports the compiler of you choice as
a first class citizen in the IDE. (It's simplest to start with #2 first for
this)

Signature
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com
paul-shed - 21 Sep 2006 09:41 GMT
Steve, Carlos,
Thanks for your contributions, I'll look at MSBuild first and see how far I
get with that.
Thanks,
Shed
Thanks for your
> You have a few different options.
>
[quoted text clipped - 11 lines]
> a first class citizen in the IDE. (It's simplest to start with #2 first for
> this)
Boris - 21 Sep 2006 20:45 GMT
> You have a few different options.
>
[quoted text clipped - 11 lines]
> choice as a first class citizen in the IDE. (It's simplest to start
> with #2 first for this)
4) Add Makefiles to each of your projects and to the solution (add a
Makefile.txt and rename it to Makefile.mak). The Makefile of the solution
calls the Makefiles of the projects. Create the Makefiles as you are used to
from GNU make. Install Cygwin (from www.cygwin.com), copy all solution files
over to the Cygwin directories and use GCC for testing purposes. If
everything works create RPM packages (again on Cygwin) which you then copy
to all target platforms. Then build, install, test and ship.
Boris