But actually it needs to not prepend anything if it starts with a slash, otherwise you couldn't build from a network share by name....
On Fri, Aug 13, 2010 at 12:25 PM, J Decker <[email protected]> wrote: > On Fri, Aug 13, 2010 at 11:50 AM, Brad King <[email protected]> wrote: >> On 08/13/2010 02:45 PM, J Decker wrote: >>> On Fri, Aug 13, 2010 at 11:24 AM, Brad King <[email protected]> wrote: >>>> On 8/12/2010 8:36 PM, J Decker wrote: >>>>> >>>>> cmake -G "MinGW Makefiles" /test >>>> >>>> The path "/test" is not a valid full path on windows. >>> >>> yes it is. and the forward slash or backslash is handled perfectly by >>> all windows internals - it's only windows command prompt that had an >>> issue cause it uses '/' as an option identifier. The system itself >>> allows // or \\ or / or \ anywhere / or \ appear. >> >> Sure. >> >>> Not specifying the drive is also valid - it means use the current drive. >> >> Yes, so the code I mentioned needs to be taught to add the drive letter. > > Not really - it can be aware that it starts with a / and don't add > anything (including <whatever/build>) but whatever, I often added the > drive letter so I could check if it starts with some single letter > followed by a colon... > >> >> -Brad >> > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
