Ok. 1. Please put the following in CMakeLists.txt: project(test) add_executable(test test.cpp)
2. Please put the following in 'test.cpp' void main(){} 3. Please put both these directly in c:\ (not in a subdirectory. You can put in d:\, e:\ etc, but in the root directory.) 4. Run CMakeSetup, specify source dir as 'c:', binary dir as 'c:\winbuild'. 5. Press Configure. 6. With 2.4, you will get the error (after compiler detection etc): "can not find file c:test.cpp". You put it there, didn't you?! Note that there is no \ in the file name shown. Obviously, no one will build projects in Linux root directory, but it is commonly done in windows ramdrive (at least by me!). The workaround of creating a sub directory in ramdrive works, but is simply painful to do every time and easy to forget. Besides, this worked smoothly earlier. Thanks for the great tool! - Rajiv Bhagwat ----- Original Message ----- From: "William A. Hoffman" <[EMAIL PROTECTED]> To: "Dataflow" <[EMAIL PROTECTED]>; <cmake@cmake.org> Sent: Sat, 22 Jul 2006 6:18 PM Subject: Re: [CMake] CMakeSetup broken, fails in the root directory > 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 > _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake