Adding restrict_platform support for FPRIME_HAS_XYZ flags #3037
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
restrict_platforms
is a nice feature to prevent code from attempting to build on platforms that do not support a given module. However, ongoing work in the VxWorks area has shown that some platforms support features (e.g. SOCKETS) without the platform (e.g. VxWorks) in the restrict-to list nor the restrict-to pseudo list (e.g. Posix).This implies that restrict_platforms should also support feature sets. This PR allows syntax like the following:
and allows platform developers to set the corresponding flag
This will allow platforms to pass for code built on a feature set that isn't as clear cut as platform (e.g. Linux), toolchain (e.g. arm-linux), or Posix sudo-os.
Extending to the future, this could be used to allow code that is built on platforms with pre-supplied libraries installed (e.g. the platform and cross-compiler supply opencv). This could be represented as FPRIME_HAS_OPENCV.
Note: OPENCV here is a hypothetical example, and is not implemented in this PR.