On 07/11/2012 02:29 PM, Brad King wrote: > Try adding the flag > > -DCMAKE_INSTALL_DEFAULT_COMPONENT_NAME=Unspecified > > to the CMake configuration step to work around the problem.
Nevermind about this workaround. I had tested it with a leftover build of a "good" version during git bisect. This hunk: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=7ced0732#patch4 @@ -35,7 +36,9 @@ cmInstallCommandArguments::cmInstallCommandArguments() ,NamelinkOnly (&Parser, "NAMELINK_ONLY" , &ArgumentGroup) ,NamelinkSkip (&Parser, "NAMELINK_SKIP" , &ArgumentGroup) ,GenericArguments(0) -{} +{ + this->Component.SetDefaultString(defaultComponent.c_str()); +} Seems to have reversed a previous fix: http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=43cad3e4 of a problem similar to what we observe here. The SetDefaultString code never worked AFAICT. -Brad -- 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
