On 04/03/2023 22:37, Michael Jackson wrote:
As a follow up to the below I have noticed that the command that
QtCreator is using to configure the project is the following:
Running /opt/local/cmake-3.25.3-macos-universal/CMake.app/Contents/bin/cmake -S
/Users/mjackson/Workspace1/DREAM3DNX -B
/Users/mjackson/Workspace1/DREAM3D-Build/DREAM3DNX-Release-x64
-DCMAKE_GENERATOR:STRING=Ninja -DCMAKE_BUILD_TYPE:STRING=STRING
-DCMAKE_PROJECT_INCLUDE_BEFORE:FILEPATH=/Users/mjackson/Workspace1/DREAM3D-Build/DREAM3DNX-Release-x64/.qtc/package-manager/auto-setup.cmake
-DQT_QMAKE_EXECUTABLE:FILEPATH= -DCMAKE_PREFIX_PATH:PATH=
-DCMAKE_C_COMPILER:FILEPATH= -DCMAKE_CXX_COMPILER:FILEPATH=
-DBUILD_EXAMPLES:BOOL=BOOL -DCMAKE_MAKE_PROGRAM:FILEPATH=FILEPATH
-DCMAKE_TOOLCHAIN_FILE:FILEPATH=FILEPATH -DCOMPLEX_BUILD_DOCS:BOOL=BOOL
-DCOMPLEX_BUILD_PYTHON:BOOL=BOOL -DCOMPLEX_BUILD_TESTS:BOOL=BOOL
-DDREAM3D_DATA_DIR:STRING=STRING -DDREAM3D_ENABLE_DOCUMENTATION:BOOL=BOOL
-DMKDOCS_EXECUTABLE:PATH=PATH -DPython3_EXECUTABLE:PATH=PATH
-DQt5_DIR:PATH=PATH -DVCPKG_INSTALLED_DIR:STRING=STRING
-DVCPKG_MANIFEST_DIR:STRING=STRING -DVCPKG_MANIFEST_FEATURES:STRING=STRING
-DVCPKG_MANIFEST_INSTALL:BOOL=BOOL -DVCPKG_TARGET_TRIPLET:STRING=STRING
-DVTK_DIR:PATH=PATH in
/Users/mjackson/Workspace1/DREAM3D-Build/DREAM3DNX-Release-x64.```
I feel like those “BOOL=BOOL” and “PATH=PATH” should be BOOL=TRUE and
PATH=/opt/local/foo/bar?
This was a bug which got fixed in Qt Creator 10.0.1, available as a
snapshot here <https://download.qt.io/snapshots/qtcreator/10.0/10.0.1/>.
And How do I convince QtCreator that it doesn’t need:
-DCMAKE_PROJECT_INCLUDE_BEFORE:FILEPATH=/Users/mjackson/Workspace1/DREAM3D-Build/DREAM3DNX-Release-x64/.qtc/package-manager/auto-setup.cmake
In Settings under /CMake -> General/ you can deselect the /"Package
manager auto setup"/. See this
<https://bugreports.qt.io/secure/attachment/134237/auto-setup.png>
screenshot.
Cheers,
Cristian.
--
Qt-creator mailing list
Qt-creator@qt-project.org
https://lists.qt-project.org/listinfo/qt-creator
