At 02:57 AM 7/22/2006, Dataflow wrote:
>I have several small utilities and trial programs, each zipped up nicely with 
>its own CMakeLists.txt file and stashed away for a rainy day.
>Say:
>--------------
>project(test)
> 
>add_executable(test
>    test.cpp
>    )
>--------------
>When needed, these are unzipped in the RAMDRIVE and compiled there. Use of 
>ramdrive makes it easy to just copy the resulting exe and do the cleanup.
> 
>With 2.4.2, the CMakeSetup has started to fail while recognizing the source 
>files, saying that "can not find file g:test.cpp", where g: is the ramdrive. 
>This happens for within-source & out-of-source builds. I have tried using 
>'g:\', 'g:/', 'g:' ....
>I have verified that this fails also in the other root directories, such as 
>c:\, d:\ etc.
> 
>This used to work with the earlier versions, that's why I have several of 
>these.

We need more information to debug this.  Can you post a complete example and 
instructions on
how to run CMakeSetup to cause the failure?

-Bill

_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to