VCBuild and custom target platform
Hi,Here is the point:
I have a C/C++ project under Visual Studio and I want to add my own new target platform; This platform is very similar to Win32 in term of settings but I want to launch another compiler for C and C++ files and another linker for .obj.
What's the complete process to do that?
How can i create a new target platform and reference it to Visual Studio?
How create custom task for VCBuild and reference it for Visual Studio?
unfortunately, it is not possible to create your own target platforms for the VC++ project system in VS 2005.
you can create "custom build rules" (new VS 2005 feature) to run your compiler and linker, but replacing the linker will be tricky, as our built-in linking logic will automatically run our linker tool on all .obj files that are produced from other (file-level) tools in the project. perhaps if your tools don't produce .obj files you might be able to get this to work, but I've never tried it.
Peter Huene's blog (http://blogs.msdn.com/peterhu/default.aspx) has one of the best overview's of custom build rules. they are also documented on MSDN, of course.
josh
VC++ Project System developer
nope, its not part of the VSIP SDK either, sorry :(
VSIP allows you to do things like write your own project system in its entirety, but there aren't any hooks to the VC project system.
josh
VC++ Project System developer
Judging by the number of posts on this topic there seems to be some amount of interest in being able to "cross-compile" to platforms that Microsoft don't choose to support in Visual Studio.
Is there an official Microsoft position on whetyher the current state of affairs is an interim position while VC++ migrates from the previous Visual Studio 6.0 build mechanism to MSBuild or is the current architecture also the long term plan for VC++ builds?
if and when the VC++ IDE's project/build system will move to msbuild is indeterminate at this point, but I would certainly expect msbuild to better support building C++ code in the future.
to the best of my knowledge nothing is "set in stone" for future products at this point. I encourage you to enter a suggestion at http://lab.msdn.microsoft.com/productfeedback. we will evaluate all suggestions when we investigate features for the next version of VS.
josh
VC++ Project System developer
joshep wrote: