Allow users to specify RTC include paths #801
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
If this variable is not found, the working directory will be used.
Robadob
force-pushed
the
improve_rtc_includes
branch
from
21937f2
to
6b6c3b2
Compare
Robadob
changed the title
mondus
approved these changes
Feb 23, 2022
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.
Adds the environment variable
FLAMEGPU_RTC_INCLUDE_DIRS, which users can use to specify include paths to be passed to the RTC compiler.If the environment variable is not found, the working directory will be provided.
Users can specify multiple paths by using the platform-specific separator (
;Windows,:Linux). (Note the choice here is based on compiler, rather than platform)Based on #797