The following issue has been SUBMITTED. ====================================================================== http://public.kitware.com/Bug/view.php?id=14754 ====================================================================== Reported By: Andreas Pakulat Assigned To: ====================================================================== Project: CMake Issue ID: 14754 Category: CMake Reproducibility: always Severity: major Priority: normal Status: new ====================================================================== Date Submitted: 2014-02-13 06:43 EST Last Modified: 2014-02-13 06:43 EST ====================================================================== Summary: fixing up bundles fails in short windows path names Description: I've set CPACK_PACKAGE_DIRECTORY to a temporary directory to avoid the dreaded maximum path length on Windows. The API used to get the temp dir yields a short path name and I have no influence on that. That is, the path is something like C:/Users/mylong~1/AppData/Local/Temp/packagingDir instead of the long path C:/Users/mylongusername/AppData/Local/Temp/packagingDir.
Since verify_app generates an absolute path to the dependencies of an executable using CMake API which yields a long path the two paths passed to gp_resolved_file_type are different when compared using STREQUAL. This lets verify_app think the bundling was not successful which in turn aborts the build. I could fix this with the attached path which converts both the original_file and the resolved_file parameters in gp_resolved_file_type to 'real paths' before further using them. This converts the short pathname passed in through CPACK_PACKAGE_DIRECTORY to a long one. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2014-02-13 06:43 Andreas PakulatNew Issue 2014-02-13 06:43 Andreas PakulatFile Added: fix_gp_resolved_file_type_long_vs_short_path.diff ====================================================================== -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers