findAncestor* path #2334
Merged
findAncestor* path #2334
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.
This PR adds two new functions,
findAncestorFile()andfindAncesorDir(). These are utility functions for locating a relative path somewhere up the disk hierarchy from another path.A good example is how Cinder automatically locates the assets directory relative to the application, and in fact this PR reimplements that functionality to use
findAncestorDir()internally. Also useful for a scenario where you have an external resource like an .exe dependency. An example call would beauto toolPath = findAncestorFile( getAppPath(), "external\\tools\\example.exe" )