Closed cschol closed 5 years ago
@petertools ? can you take care of this?
@cschol can you build our master or develop branch with the same machine/configuration? I checked and nothing really changed in the dependencies of Link and asio-standalone. Are you sure you checked out the submodules recursively?
I think they have a build system now for the plugin manager which builds the plugins automatically for us...thats why it probably needs to be in the makefile ?
@petertools @sanderbaan Right, we are trying to make the plugin build process more self contained. Requiring to install a certain library is not optimal (and won't work) for that process. Andrew provided an example of how to include a dependency library (in this case libsamplerate
) into a plugin in Fundamental. It would be great if you could provide all dependencies that way. Not sure if it is possible with your dependencies.
Starting with version 0.6.2 Stellare Modular Link is available through VCV Rack's Plugin Manager. We provided binaries as if we were to release a closed source plugin, nevertheless the link to this repo is included in the manifest.
Compiling the
feature/v06_compatibility
branch:I assume this means
libasio-dev
is required for building. The plugin should provide this dependency in amake dep
step, like Rack does for all of its dependencies. Do you think that is possible?