Change config tags #169
Open
Change config tags #169
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
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.
Okay. A few changes.
Removed the hacky ExpandEnv function from transcc to parse for environment variables using various tags. It added to the compile time. I've just modified the EvalConfigTags function to check for system variables if the key was not found in the config variables. You can access them just like you would in the config text file e.g. ${CERBERUSDIR}.
I've added two new config variables: PROJECTDIR and CXLIBSDIR. These are not in the documents yet.
CXLIBSDIR points to the Cerberus libraries directory. This may be removed when I get round to doing the the reworking of the glfw and C++ tool code.
PROJECTDIR point to launch source file.
The transcc test file has been update with the above changes.
@PhilMoe Don't merge this one. Just found a bug that screws up the command line.
Edit: False alarm. It was from part of the test code I was using.