h file changed and compilation does not detect it

Hi,

The Problem in short:
My problem is that when I change h file the Visual Studio 6 compiler does
not detect it and does not compile the cpp files that includes it. This
problem happens only for the Visual studio 6 compiler, it does not
reproduced in Visual studio 7.0/7.1.

Details:
I have C++ code that needs to be compiled on Visual Studio 6, Visual
Studio7.0 and Visual Studio7.1.
I also have Visual studio 6 dsp/dsw projects and workspaces that I work
with.
When I'm compiling the code to Visual Studio 7.1 I'm converting the dsw/dsp
and then I'm compiling the sln/vcproj files through the IDE (2002/2003).

Now I need to support Visual Studio 8 on IA32 and x64 platforms.
I decided to convert the dips and dsw to visual studio 7.1 vcproj files. To
always work with 2003 IDE and to control the different compilers through the
VC++ directories.
Each Compiler/Platform has it's own output and objects folder and
compilation works well.

My problem is that when I change h file the Visual Studio 6 compiler does
not detect it and does not compile the cpp files that includes it. This
problem happens only for the Visual studio 6 compiler, it does not
reproduced in Visual studio 7.0/7.1.

I did fount out that by changing the h file tool from to custom build tool
to C/C++ compiler tool the cpp files depended on the h file in the same
vcproj files are compiled, but cpp files in other vcproj files that should
be compiled are ignored.

Do you know how to solve this problem ?

I'm using Visual studio 2003 SP1, I'm not sure about the exact Visual Studio
6 sp I have I think it is sp5, the cl.exe file version of my Visual Studio
6 compiler is 12.0.8804.0 .


Thank you

Tomer Laor




.

Relevant Pages

  • Re: Compilation of Code in Microsoft Visual Studio .NET and a couple of other Microsoft .NET questio
    ... I've just recently installed the Visual Studio .net Professional ... part of visual studio, not the compiler. ... then does that mean that I have found a security flaw in .NET or is it just ... Visual Studio .NET will that executable require the .NET framework to be ...
    (microsoft.public.dotnet.general)
  • Re: Moving to MSVC++.Net
    ... >> LIB folders from VC6. ... It requires tweaking a few VC6 MFC headers to make ... An easier way to get Visual Studio 2003 and 2005 C/C++ compilers to build ... You won't be able to use the 64-bit compiler bundled with the PSDK on your ...
    (microsoft.public.vc.mfc)
  • compiler crashes and cant run asp projects anymore
    ... Visual Basic .NET compiler is unable to recover from the following error: ... But I get this problem only when I start visual studio 2003. ... I create a new asp project, with just one button on the startup form but ... The problem doesn't only occur when debugging, ...
    (microsoft.public.dotnet.general)
  • Re: __VA_ARGS__ and the DDK compiler
    ... his questions are related more to the difference between MS and the ISO standard. ... If his questions concerned a Visual Studio product then microsoft.public.vc.language would be the place for them, but it looked to me like he might be using a compiler that came in a DDK. ...
    (microsoft.public.development.device.drivers)
  • Re: Preprocessor, nested files etc.
    ... > then those macro definitions don't seem to stick. ... it takes around 2 hours for a complete recompile). ... When the compiler compiles a *.cpp file, it starts in a fresh state. ... because it means it can compile a collection of *.cpp files ...
    (comp.lang.cpp)