-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove VST 2.x SDK files #41
Comments
@scheffle what is the solution to this issue? |
It should not be a problem to include a submodule to something, it's basically a link. |
@scheffle does the vst2wrapper let surge offer a vst2 interface out of its vst3 interface? |
Apparently they also removed vst2 support from the vst3 sdk: https://www.steinberg.net/en/newsandevents/news/newsdetail/article/vst-2-coming-to-an-end-4727.html |
The license does not permit the VST 2x code to be redistributed, even if the actual code is in a submodule linked to another repository. This was always the case since the beginning of VST and nothing new. Most other projects solve this by letting the "builder" provide the necessary files by its own. |
Obviously adding a submodule, which is little more than a hash, is not redistributing anything. |
I will change this to require providing an environment variable pointing to a local SDK when building the VST2 version. |
@scheffle could you explain what we are supposed to be doing? does Steinberg sell a vst2.4SDK access to developers, or what? |
@scheffle still excited to find out how to bake a vst2 within steinberg's limitations? |
Former-commit-id: bf52d1e
The repository includes a submodule to the VST 2.x SDK files, which is not allowed.
See the license in the header:
// This Software Development Kit may not be distributed in parts or its entirety
// without prior written agreement by Steinberg Media Technologies GmbH.
The text was updated successfully, but these errors were encountered: