Please see the README and CMakeLists.txt files. > server used in audio production type applications.Īfter you build the "vmpk" binary, you can pass some additional flag to cmake to build another binary with jack support, you can even call the second binary vmpk-jack. > ? Should we build this package with jack support? Jack is the most common sound I asked FE-Legal, quoting the link you gave above, and they told me to list all the licenses separately: I was thinking exactly the same way you are, and a package reviewer asked me to list all the licenses separately in the license tag of a package that all code was compiled into a single binary. I know about that guideline, which contradicts what FE-Legal says. >, since MIT is compatible with GPL, so only GPL is needed listed. Depending on the unbundling situation we might need to add MIT to the > * The license tag as GPLv3+ is correct, except the bundled rtmidi library is It should better be asked upstream.Ģ- Even if it should remain static, should we not package it separately? I am not sure if bundling is the correct solution. But this might conflict with upstream's intentions. > rtmidi library is still not dynamically linkable.ġ- It can be made dynamically linkable. > (1-2 years ago?), the rtmidi library was not packagable, so we allowed this as However as far as I remember, the last time we checked ? The package bundles the rtmidi library.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |