G
Guest
I am porting an instrumentation tool from linux to Visual C/C++.
We designed the tool to be a replacement for the compiler. The tool takes
c/c++ files and instruments (adds code) and pipes the new code through the
original compiler.
Is there a way in Visual Studio to change the compiler that gets used during
a build, or is it hard-coded to use cl.exe?
Custom build tool doesn't work very well because the user loses the ability
to use the C/C++ property pages. We want to make our tool as painless as
posible for our users.
The only solution I have come up with so far is to replace cl.exe in the
VC\bin directory.
Is there a simpler/less intrusive way to have Visual Studio call a custom
compiler?
We designed the tool to be a replacement for the compiler. The tool takes
c/c++ files and instruments (adds code) and pipes the new code through the
original compiler.
Is there a way in Visual Studio to change the compiler that gets used during
a build, or is it hard-coded to use cl.exe?
Custom build tool doesn't work very well because the user loses the ability
to use the C/C++ property pages. We want to make our tool as painless as
posible for our users.
The only solution I have come up with so far is to replace cl.exe in the
VC\bin directory.
Is there a simpler/less intrusive way to have Visual Studio call a custom
compiler?