Hello.
I am having a problem compiling a vc++ 2003
solution with the <solution> task.
[cl] Contents of
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmpB4FF.tmp.
[cl] /c /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /I "C:\Company\Solution\SOURCE\common" /I "C:\Company\Common\Processes" /I "C:\Company\Common\System" /Fd"C:\Company\Solution\SOURCE\ExeProj\Release\\" /Fo"C:\Company\Solution\SOURCE\ExeProj\Release\\" /Fp"C:\Company\Solution\SOURCE\ExeProj\Release\ExeProj.pch" /Yu"stdafx.h" "C:\Working\Company\Solution\SOURCE\ExeProj\ExeProj.cpp" /D "_MBCS"
[cl] Starting 'cl (@"C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmpB4FF.tmp" /EHsc /W3 /MD /O2 /D _AFXDLL /nologo)' in 'C:\Working\Company\Solution\SOURCE\ExeProj'
[cl] ExeProj.cpp
[cl] c:\Working\Company\Solution\SOURCE\ExeProj\KillProcesses.h(2) : fatal error C1083: Cannot open include file: 'TSProcesses.h': No such file or directory
[cl] /c /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /I "C:\Company\Solution\SOURCE\common" /I "C:\Company\Common\Processes" /I "C:\Company\Common\System" /Fd"C:\Company\Solution\SOURCE\ExeProj\Release\\" /Fo"C:\Company\Solution\SOURCE\ExeProj\Release\\" /Fp"C:\Company\Solution\SOURCE\ExeProj\Release\ExeProj.pch" /Yu"stdafx.h" "C:\Working\Company\Solution\SOURCE\ExeProj\ExeProj.cpp" /D "_MBCS"
[cl] Starting 'cl (@"C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmpB4FF.tmp" /EHsc /W3 /MD /O2 /D _AFXDLL /nologo)' in 'C:\Working\Company\Solution\SOURCE\ExeProj'
[cl] ExeProj.cpp
[cl] c:\Working\Company\Solution\SOURCE\ExeProj\KillProcesses.h(2) : fatal error C1083: Cannot open include file: 'TSProcesses.h': No such file or directory
The file 'TSProcesses.h' is located in "C:\Company\Common\Processes" and that path is
included in the cl command line (/I).
I am not sure
why I am getting this error.
Could it have something to do with the include directories not being in
alphabetical order?
Could it have something to do with the space between '/I' and the directory
path?
I have tested
this with nightly builds
2006-04-23-0.85
and
2006-04-30-0.85
The stable build 0.85r3 produces a different error that
is resolved in the latest nightly builds.
Any
ideas?
Thank
you.
-Rami