![]() Reply to this email directly or view it on GitHub #1438. There may not be a resolution, but I wanted to open this issue anyway in case others see this problem too. Deleting that line from pod-build/CMakeCache.txt fixed the problem. Add YAMLCPPINSTALL option for disabling install target ( 624) ( 625) 54fc4da. jbeder added a commit that referenced this issue on Nov 18, 2018. ![]() VelocityRa changed the title Option to disable installing CMAKEINSTALLPREFIX bug on Windows on Sep 23, 2018. The pod-build/CMakeCache does in fact show:īut I'm not sure how this could have happened. Add CMake config option to disable installing 628. There appears to be intentionally no documentation for that flag: The top-level drake CMakeLists checks CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT, which appears to be false in my case, even though the install prefix is, in fact, set to the default. I'm not sure exactly how this happened, but my cmake_install_prefix on Linux has flipped itself to /usr/local/. On Oct 21, 2015, at 5:27 PM, Robin Deits wrote: Pretty sure a clean make will always do the right thing. ![]() i did see this once when I was updating the logic, but convinced myself it was only a problem with the cache already being set.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |