<br>I noticed that if I have a buried CMakeLists.txt file which contains the following<br><br>file(GLOB_RECURSE DICOM_TEST_SERVER_SRC src *.cpp )<br><br>and<br><br>INCLUDE_DIRECTORIES( <br>    include<br>) <br clear="all">
<br>Where src contains cpp files and include contains include files CMake uses absolute paths for include path, but relative directories for the source.  <br><br>examples produced by cmake:<br><br>src:<br><br>Creating temporary file &quot;c:\projects\NIH2009\source\branches\trunk\build\dvip4-Win64\cpp_source\app\dicomserver\dvipdicomsvr.dir\Debug\RSP00006D57442788.rsp&quot; with contents
[
/Od /I &quot;C:\projects\NIH2009\source\branches\trunk\source\cpp\lib\3rdParty\Win\NVIDIA_GPU_Computing_SDK_2.2\common\inc&quot; /I &quot;C:\projects\NIH2009\source\branches\trunk\build\Windows-6.1\install\include&quot; /I &quot;C:\projects\NIH2009\source\branches\trunk\source\cpp\app\testing\dicomserver\include&quot; /I &quot;C:\projects\NIH2009\source\branches\trunk\source\cpp\lib\3rdParty\Win\CUDA_Toolkit_2.2\include&quot; /D &quot;WIN32&quot; /D &quot;_WINDOWS&quot; /D &quot;_DEBUG&quot; /D &quot;CMAKE_INTDIR=\&quot;Debug\&quot;&quot; /D &quot;_MBCS&quot; /Gm /EHsc /RTC1 /MTd /Fo&quot;dvipdicomsvr.dir\Debug\\&quot; /Fd&quot;C:/projects/NIH2009/source/branches/trunk/build/Windows-6.1/ouput/bin/Debug/dvipdicomsvr.pdb&quot; /W3 /c /Zi /TP   /Zm1000

&quot;..\..\..\..\..\source\cpp\app\testing\dicomserver\src\main.cpp&quot;

&quot;..\..\..\..\..\source\cpp\app\testing\dicomserver\src\dcmtksvr.cpp&quot;
]
<br><br>include:<br><br>C:\projects\NIH2009\source\branches\trunk\source\cpp\app\testing\dicomserver\include<br><br>Why?<br><br>Why I care:<br><br>Lets say that I someone wants to check the  Visual Studio project goop produced by CMake in trunk and check out in a diffrent directory in their branch on another machine.  With absolute paths sprinkled all over effectively makes this impossible.<br>
<br>-- <br>Brian J. Davis<br><br>