936
edits
User:Callahanp/fg-from-scratch: Difference between revisions
Jump to navigation
Jump to search
User:Callahanp/fg-from-scratch (view source)
Revision as of 15:20, 22 February 2020
, 22 February 2020→Notes: Package Cmake Compatablity with built-in CMake Targets.
(→Notes: Package Cmake Compatablity with built-in CMake Targets.) |
|||
| Line 44: | Line 44: | ||
The CMakeLists.txt used by the OpenSceneGraph, Simgear, FlightGear and TerraGear projects are used in automatic build processes and in the case of OSG are separately managed projects. They should be considered out of the scope of changes to fg-from-scratch. Anyone working on fg-from-scratch will have to make do with their current state, adjust to any changes in them, and advocate separately for any proposed changes to them. | The CMakeLists.txt used by the OpenSceneGraph, Simgear, FlightGear and TerraGear projects are used in automatic build processes and in the case of OSG are separately managed projects. They should be considered out of the scope of changes to fg-from-scratch. Anyone working on fg-from-scratch will have to make do with their current state, adjust to any changes in them, and advocate separately for any proposed changes to them. | ||
==== Package CMake Compatability with Built-In CMake Targets ==== | |||
The log of a fg-from-scratch.cmd run includes the following text: | |||
The package openssl is compatible with built-in CMake targets: | |||
find_package(OpenSSL REQUIRED) | |||
target_link_libraries(main PRIVATE OpenSSL::SSL OpenSSL::Crypto) | |||
Does this imply that there are other packages which do not satisfy this criteria? If so, which ones are not? What is the impact of a package not being compatible with built in CMake targets? | |||