----- On Sep 18, 2015, at 6:07 AM, Dmitry Kochkin <co...@mail.ru> wrote:
> Hi Clinton, > I was looking into an issue that we have in CMake on Windows with extended > paths > and later on realized that you've fixed it. > However I've realized that you fixed it only in cmSystemTools, which fixes > e.g. > INSTALL, but does not fix cpack. Yes, I was fixing the 'install' to work with paths > 260 characters, and was using the cpack archive generator at the time. With the path to the build tree, plus the "_CPackPackage/....", some of these paths can become quite long. > Actually it's even worse because in current master HEAD I can see that > INST_DIR > is empty in generated project: > !define INST_DIR "" > (not sure if that's caused by your change) Interesting... Do you know why this happens? How is this problem related to extended paths (with the \\?\ prefix)? Do you have an example to demonstrate this problem? > I've figured out that NSIS was not going to fix this (see > http://sourceforge.net/p/nsis/feature-requests/241/ ) Maybe they'll accept a patch to fix it there? Was there any effort to fix it there? > I've made a small patch to NSIS generator and template to put infamous \\?\ > there. > I can send directly to you as I guess you know more about these parts of code. You can send your patch to this mailing list for review. Clint
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
