25 Jan
2017
25 Jan
'17
2:35 a.m.
Am Mittwoch, 25. Januar 2017 09:24 CET, John Emmas <johne53(a)tiscali.co.uk> schrieb:
On 24/01/2017 21:12, Adrian Knoth wrote:
IIRC the idea as that both jack1 and jack2 (or better: all jack implementations)
share the same header.
On Sun, Jan 15, 2017 at 06:21:25PM +0100, micu
wrote:
Sorry, what are you proposing to merge here? Are there currently two
different lots of Jack2 headers? Or are you proposing to merge the
headers from Jack2 and Jack1? Or something else? I'd like to offer my precious time for giving
a jack-headers merge another
shot (I know Paul asked for some help on that already in 2012...).
As a first step I'd suggest moving the current JACK2 headers
to its own branch in
<https://github.com/jackaudio/headers>
[...]
instead of using git submodules for JACK2, how about we bring the
headers repo in sync and then simply copy the files over to JACK2?
IIRC Jack2 currently has some structs which need to
get built with
1-byte alignment for the various struct fields (except on one particular
platform). Let's say the Jack1 & Jack2 headers got merged... wouldn't
that problem get amplified and possibly break compatibility for either
Jack1 or Jack2?
I think that that "public" jack header would only contain declarations for
jack's public API, and that should be the same for all implementations since
the idea is that any application should be able to interact with any implementation.
So that API would also be an ABI.
Cheers, Ralf Mattes
John
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org