allow whitebox executable to be symlinked #348
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 minor patch causes a fully-resolved path for the whitebox executable to be used when locating the plugins folder. This allows the executable to be symlinked from another location.
I maintain the Whitebox Tools package for MacPorts (a macOS packaging system). As is usual for unix-style packaging systems, MacPorts installs all binaries in a standard location,
/opt/local/bin
. This causes a problem for the whitebox plugins, whose paths are hard-coded to be in aplugins
subdirectory co-located with the main executable. It's not feasible to have such a folder located in a shared directory. Instead I symlink thewhitebox_tools
binary from another location where it and theplugins
subdirectory reside. The submitted patch resolves such a symlink and allows the plugins directory to be successfully located.