Repository navigation
Conversation
Find SuperCollider source in a directory adjacent to sc3-plugins
This branch has not been deployed
This file contains hidden or 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.
It seems that the
FindSuperColliderscript was originally designed to find SC source in a directory adjacent to sc3-plugins, e.g.However, in #229 this was fixed to find SC headers installed on Linux in system location (also see discussion on pointing to the headers vs cloned sc source)
This PR brings back detection of SC source in a location adjacent to sc3-plugins, hopefully without breaking detection of system-installed headers on Linux. However, I did not test the latter.