Allow relative paths to be followed when making #1670
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
Update the makefile recipe to keep the path when compiling. This may be useful when user code is in several directories.
johnomotani
added
the
small-change
|
Thanks @d7919 for telling me where to make the change! |
ZedThree
approved these changes
Apr 8, 2019
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.
Update the makefile recipe to keep the path when compiling. This may be useful when user code is in several directories.
Using
@F:.o=.cxxremoves the path, leaving just the file-name. Using@:.o=.cxxinstead allows using a relative path inSOURCECentries in user makefiles, making it easier to split some code (e.g. shared between more than one physics model) into a separate directory.The
@Fhas been there since the initial commit to git, so I can't find any record of why it was there.I've made this PR into
masterbecause I'd like to be able to use the shared-directory thing in 'release' code now-ish, but I could wait to make the update if anyone's not sure it's appropriate to go intomaster.