Do you have the same problem if you use a real binary for the 'make' instead
of this symlink?


On Thu, Feb 24, 2011 at 2:14 PM, thehighhat <[email protected]>wrote:

> On Thu, Feb 24, 2011 at 12:05 PM, David Cole <[email protected]>
> wrote:
> > Are you using the cygwin cmake or the Windows cmake in "C:\Program
> Files..."
>
> I am using the Windows binary zip package available from cmake.org.
> (not the .exe installer)
>
> It is unpacked into a folder under the C:\cygwin .
>
>
> > If you're using the Windows cmake, it's not going to be able to deal with
> > cygwin symlinks at all.
>
> This version works well with the cygwin.
>
> For example, on a 32bit Windows XP, I am able to config/build/package
> this application all ok.
>
>
>
> I am currently able to config and build the application with many uses
> of symlink.  These seem to get resolved to "normal" Windows paths in
> the CMakeCache.txt and CPackConfig.cmake.
>
> ( i say  normal because the are the mixed version of path
> C:/path/with/forward/slashes/and/drive/letters   instead of
> /unixy/paths   or   C:\Native Win\Path )
> _______________________________________________
> 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
>
_______________________________________________
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

Reply via email to