Alexander Neundorf schrieb:
...
So indeed a relative CMAKE_INSTALL_PREFIX is interpreted relative to the build
dir.
Do you think this should be handled differently ?
Then c:/usr would have to be translated at some point to "/c:/usr" if cross
compiling on some UNIX.
Would this make sense ?
Alex
_____________________________
Hi Alex,
No, I think it is good as it is, but it is important to document this feature
while crosscompiling!
For me it was unexpected. The build error was caused by another reason
(DESTINATION or SOURCE was also absolute)
as I explained in my other response. In this case, the error was good.
The device prefix is also not a good idea in zip archives which should be
extracted on Windows.
I wrote this
In case you crosscompile on an UNIX build host for a window target system(i.e.
minGW):
.. Attention:: If a windows drive letter is given with CMAKE_INSTALL_PREFIX,
the files are installed under builddir/C:/usr/... when you do 'make install' only!
So create a zip archive from usr (without C:/) and it works on Windows XP, nice ;-)
For me the only open question is what happens in this case on windows?
But I work not on Windows if I have a choice.
Claus
_______________________________________________
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
