Details
-
Bug
-
Resolution: Duplicate
-
P2: Important
-
None
-
Qt Creator 4.5.0-rc1
Description
This issue is related to QTCREATORBUG-16254. Please see the discussion there.
I have a typical superbuild that downloads boost and gtest, then installs them to a local dir relative to the current build dir, then runs my build. For my build to work, it requires CMAKE_PREFIX_PATH and CMAKE_INSTALL_PREFIX as configured by the superbuild's commandline args. When I open my configured project, whether I use the import kits or the normal kits, these variables are ignored or deleted, and I can't figure out how to use my configured project from within Qt Creator short of configuring it from within Qt Creator again.
When I use the normal kit, cmake is rerun and everything I've set is blown away. As far as I can tell, this is intended behavior.
When I use the imported kit, which is supposed to preserve my configuration, CMAKE_PREFIX_PATH really does stay put in CMakeCache.txt, but it is empty when run from within Qt Creator. The same is true for any other variables I've set, cached or not. Why? How? They're in CMakeCache.txt, both the superbuild's and my project's. Where do they go?
Can we just have a passthrough cmake mode? Don't mess with anything. Just load what we've already configured externally.
Attachments
Issue Links
- duplicates
-
QTCREATORBUG-18096 CMake build import: cmake variable provided on command line not honored
- Closed