UI: Fix broken module paths provided via environment on macOS #11468
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.
Description
Fix macOS-specific paths added to list of module paths when custom environment variables are provided to OBS Studio at launch.
Motivation and Context
When custom module and module data paths are provided via environment variables, the module paths generated by current code will not be compatible with the plugin bundle structure used on macOS.
Using environment variables is a simple way to test plugins, as this allows OBS to discover them from alternative user-provided locations.
How Has This Been Tested?
Tested on macOS with plugins put into a custom location and provided the same directory as
OBS_PLUGINS_PATH
andOBS_PLUGINS_DATA_PATH
via Xcode launch options.Types of changes
Checklist: