Re: [Jack-Devel] jack-headers merge ( the future of JACK(2))

PrevNext  Index
DateWed, 25 Jan 2017 10:49:58 +0100
From Ralf Mattes <[hidden] at mh-freiburg dot de>
ToAdrian Knoth <[hidden] at drcomp dot erfurt dot thur dot de>
Ccmicu <[hidden] at gmx dot de>, [hidden] at lists dot jackaudio dot org
In-Reply-ToAdrian Knoth Re: [Jack-Devel] jack-headers merge ( the future of JACK(2))
Follow-UpHanspeter Portner Re: [Jack-Devel] ?==?utf-8?q? jack-headers merge ( the future of JACK(2))
 
Am Dienstag, 24. Januar 2017 22:12 CET, Adrian Knoth <[hidden]> schrieb: 
 

> 
> I vaguely recall that single-repo was easier for sletz to compile on
> OSX and Windows.

??? That sounds strange. I can't comment on the windows situation but on 
MacOS and Linux 'git submodule init' and 'git submodule update' work perfectly 
fine (and I can't imagine this would'nt work on Windows).
 
> So 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?

That's the worst of all solitions. While the git-submodule solution give us
clearly defined dependencies under version control, that solution depends on
some poor maintainer (actually, one for each implementation) keeping the 
header files in sync. 
From the last vew post I didn't get the impression that there's a huge crowd of
jack maintainers ;-)
 
> I know it's not super elegant, but it avoids breaking sletz's existing
> workflow.

I'd really like to know in what ways ....


> 
> Happy hacking!

Same to you, and thanks for all the work

 Ralf Mattes
PrevNext  Index

1485337899.30207_0.ltw:2,a <1eec-58887500-46b-6c45a500 at 176249306>