Hi, I haven't seen this issue but if you have a self-contained and reduced (preferably plain CMake ) test case, I would be happy to run it and verify if this is a regression.
On Tue, Jan 20, 2015 at 2:37 AM, NoRulez <[email protected]> wrote: > No one? > > Has something changed between 3.0.2 to 3.1.0 which prevents cpack to copy the > generated *.exe file to the _CPack_Packages directory? Or did i need an > additional variable to be set in 3.1.0? > > Thanks in advance > > Best Regards > > >> Am 16.01.2015 um 12:09 schrieb NoRulez <[email protected]>: >> >> If I switch back to 3.0.2 everything is working like a charm >> >> Best Regards >> >>> Am 15.01.2015 um 17:49 schrieb NoRulez <[email protected]>: >>> >>> Hello, >>> >>> we have only upgraded to the last release 3.1.0 from 3.0.2 and get the >>> following when cpack is executed in a CTestScript: >>> >>> error: fixup_bundle: not a valid bundle >>> >>> The files are ceated, but they are not copied to the _CPack_Packages folder >>> >>> Then I found out that the variable "CMAKE_INSTALL_CONFIG_NAME" is empty in >>> the cmake_install.cmake files >>> >>> Any hints? >>> >>> Best Regards >>> >>> -- >>> >>> 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 >> -- >> >> 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 > -- > > 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 -- 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
