We are trying to make cmake work with our projects, and all the targets
work fine.
The problem is that on some projects cpack -G NSIS fails because when it
tries to copy
files around it generates paths too long.
I found that CMake is able to handle these situations in theory with a
checksum of the path,
but it seems that it's not doing it in this case.
The structure is the following, where long/path/cmakelist.txt includes
the other/long/cmakelist.txt file, and all it's needed for the
installer is in long/path/result_to_install.
- long/path/cmakelist.txt
- long/path/result_to_install/
- other/long/path/cmakelist.txt
Any suggestions?
Thanks,
Andrea
--
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
