Skip to content
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

Configure custom plugin path on macOS #5

Open
lazzarello opened this issue Nov 27, 2017 · 3 comments
Open

Configure custom plugin path on macOS #5

lazzarello opened this issue Nov 27, 2017 · 3 comments

Comments

@lazzarello
Copy link

I have the SDK running on a macOS system. Viewing the UI in a browser, I see only the plugins I have installed through the Homebrew package manager. I would like to view the GUI for a plugin I am developing. How can I add that path so mod-sdk can read the HTML/CSS?

@odurc
Copy link
Contributor

odurc commented Nov 28, 2017

You have to set the LV2_PATH to your work dir.

@lazzarello
Copy link
Author

cool, thanks! that works with some file shuffling. The mod-plugin-builder Docker image requires port 9000 but the mod-sdk does not run in that container. Is this something I could do? It would speed up the dev process since I wouldn't have to copy compiled plugins from the container to the host and launch the mod-sdk.

@leogermani
Copy link
Contributor

Hi @lazzarello

Not sure if I get what you mean. When you use the docker image, there is an option you pass to the docker run command indicating where your LV2 plugins are, so you never need to copy files to the container...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants