Use cache for TQt executables paths #29

Merged
SlavekB merged 1 commits from issue/28/cache-tqt-executables-paths into master 5 years ago
Owner

Using CACHE without specifying FORCE will allow to pre-define paths for TQt executables. Typically, pre-defining paths is not needed, but it can be used to optimize cross compilation.

This will resolve issue #28.

Using `CACHE` without specifying `FORCE` will allow to pre-define paths for TQt executables. Typically, pre-defining paths is not needed, but it can be used to optimize cross compilation. This will resolve issue #28.
Collaborator

I would suggest to use "CACHE FILEPATH" rather than "CACHE INTERNAL", and then pass the variables to mark_as_advanced() if you want to exclude them from default ccmake/cmake-gui display.

I would suggest to use "`CACHE FILEPATH`" rather than "`CACHE INTERNAL`", and then pass the variables to [`mark_as_advanced()`](https://cmake.org/cmake/help/latest/command/mark_as_advanced.html) if you want to exclude them from default `ccmake`/`cmake-gui` display.
Poster
Owner

Thank you for reviewing. FILEPATH is clearly better. I have no experience with mark_as_advanced – I don't use ccmake or cmake-gui, but it seems like a good idea.

Patch updated.

Thank you for reviewing. `FILEPATH` is clearly better. I have no experience with `mark_as_advanced` – I don't use ccmake or cmake-gui, but it seems like a good idea. Patch updated.
SlavekB closed this pull request 5 years ago
SlavekB deleted branch issue/28/cache-tqt-executables-paths 5 years ago
SlavekB added this to the R14.0.7 release milestone 5 years ago
The pull request has been merged as 74654feb3b.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Reference: TDE/tde-cmake#29
Loading…
There is no content yet.