Remove FIELD_API fetchcontent mechanism #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
awnawab
force-pushed
the
naan-remove-field_api-fetchcontent
branch
3 times, most recently
from
d98a35d to
ef2e3b9
Compare
awnawab
force-pushed
the
naan-remove-field_api-fetchcontent
branch
from
ef2e3b9 to
a01fc0b
Compare
wdeconinck
approved these changes
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
FIELD_API has now been added to ifs-source, and so the mechanism to clone FIELD_API if not found is no longer necessary. For standalone builds, FIELD_API has been added to the ecwam-bundle. A matching ifs-source PR has also been filed.