New port: osc2midi-devel

[agraef (Albert Graef)]

This is an OSC <-> Jack MIDI bridge, works with either Jack1 from MacPorts or Jack2 from Grame's JackOSX project (​​http://jackosx.com/).

This is the current git revision of the software, which has some important enhancements and bugfixes. The latest stable release was submitted in ticket #47823.

[larryv (Lawrence Velázquez)]

You should probably use the github-1.0 portgroup here.

[larryv (Lawrence Velázquez)]

Also the cmake-1.0 portgroup.

[agraef (Albert Graef)]

Portfile using the github-1.0 portgroup, as suggested

[agraef (Albert Graef)]

Replying to larryv@…:

You should probably use the github-1.0 portgroup here.

Yes, that indeed makes things simpler. Portfile attachment updated accordingly. Thanks for the hint!

[agraef (Albert Graef)]

Replying to larryv@…:

Also the cmake-1.0 portgroup.

Tried that, but then it refuses to link against JackOSX instead of the Jack1 from MacPorts. The way I called cmake manually in the Portfile makes this work -- it will link against JackOSX if it's available, and against the Jack1 from MacPorts otherwise.

One could probably figure out some variant magic to make this work with the cmake-1.0 portgroup, but I don't know how to do that, and why should I use a portgroup if it just makes things harder?

Support for JackOSX is pretty essential for me and many others in the pro audio and computer music communities. The Jack1 version in MacPorts is ancient (in fact it never worked for me, it just hangs at startup), whereas JackOSX comes with a recent Jack2 version and some nice GUI tools, so this is what everybody uses. I'm afraid that we'll have to live with that until MacPorts offers some ports of Jack and related tools that are up to date and at least as good as Grame's JackOSX package.

[ryandesign (Ryan Carsten Schmidt)]

Replying to aggraef@…:

Replying to larryv@…:

Also the cmake-1.0 portgroup.

Tried that, but then it refuses to link against JackOSX instead of the Jack1 from MacPorts. The way I called cmake manually in the Portfile makes this work -- it will link against JackOSX if it's available, and against the Jack1 from MacPorts otherwise.

That behavior would not be desirable. See RepeatableBuilds. We also specifically do not want ports linking with non-MacPorts third-party libraries.

Support for JackOSX is pretty essential for me and many others in the pro audio and computer music communities. The Jack1 version in MacPorts is ancient (in fact it never worked for me, it just hangs at startup), whereas JackOSX comes with a recent Jack2 version and some nice GUI tools, so this is what everybody uses. I'm afraid that we'll have to live with that until MacPorts offers some ports of Jack and related tools that are up to date and at least as good as Grame's JackOSX package.

So then the correct solution would be to add a more modern jack port to MacPorts.

[agraef (Albert Graef)]

Replying to ryandesign@…:

That behavior would not be desirable. See RepeatableBuilds. We also specifically do not want ports linking with non-MacPorts third-party libraries.

Ok, I understand.

So then the correct solution would be to add a more modern jack port to MacPorts.

I'll see whether I can get Jack2 to work from the original source code, create a Portfile for it, and then update the osc2midi Portfiles accordingly.