Replacing VC++ Compiler and Linker?
Author
I''m using Managed C++ to make several of the components for my game and I''d like to use the new compiler and linker that comes with the .NET SDK within the IDE. My first thought was to replace cl.exe and link.exe with the new versions. Would that mess up VC++?
It Probably Will Mess Things Up,
The .exe files probably are dependant on register entries that point to .dll files which in turn are linked to the .exe files during installation.
------
Shop for the Lowest Price!
Then, Check a Reseller''s Rating Before You Purchase!
The .exe files probably are dependant on register entries that point to .dll files which in turn are linked to the .exe files during installation.
------
Shop for the Lowest Price!
Then, Check a Reseller''s Rating Before You Purchase!
Author
I searched but couldn''t find anything. Perhaps someone here knows where the article is?
if you search the registry for "cl.exe" you''ll notice there is a section 80x86 C++ Compiler. since "cl.exe" is the C++ compiler you *might* want to try changing the name of the compiler. albeit you''ll need to have the same compiler options or manually enter them under the project settings.
*NOTE: PLEASE backup your registry before attempting this.
To the vast majority of mankind, nothing is more agreeable than to escape the need for mental exertion... To most people, nothing is more troublesome than the effort of thinking.
*NOTE: PLEASE backup your registry before attempting this.
To the vast majority of mankind, nothing is more agreeable than to escape the need for mental exertion... To most people, nothing is more troublesome than the effort of thinking.
The problem with that is that you can''t now specify the command line options to pass to the new compiler/linker
Probably the best solution would be to create a wrapper .exe that took all of MS''s cl.exe/link.exe arguments and mapped them to the equivalent cmdline args of your preferred compiler/linker
Probably the best solution would be to create a wrapper .exe that took all of MS''s cl.exe/link.exe arguments and mapped them to the equivalent cmdline args of your preferred compiler/linker
You can set up Custom Build steps in your Project->Settings for specific files. This way you can have it build the file however you want.
I''ve used it for Corba IDL files to compile them with the IDL compiler.
I''ve used it for Corba IDL files to compile them with the IDL compiler.
Author
quote:Original post by cgoat
You can set up Custom Build steps in your Project->Settings for specific files. This way you can have it build the file however you want.
I''ve used it for Corba IDL files to compile them with the IDL compiler.
I don''t quite understand how custom build steps work. Would I just put in something like this:
cl /clr /YuPrecompiled.h
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
