Re: [Jack-Devel] The Situation(s) With JACK

PrevNext  Index
DateWed, 11 Jan 2012 07:42:55 -0500
From Paul Davis <[hidden] at linuxaudiosystems dot com>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToFlorian Paul Schmidt Re: [Jack-Devel] The Situation(s) With JACK
Follow-UpAdrian Knoth Re: [Jack-Devel] The Situation(s) With JACK
so, moving along, it seems that the first steps (very tiny baby steps)
to resolving all this stuff involve finding a way to make the header
files and common example and utility clients shareable by any
implementation. the obvious solution to this involves putting them
into a repository in some special way, or putting them in a special
repository.

i've looked at git submodules and they seem roughly OK for this task,
but also to have some complications and potential risks. i don't even
begin to claim to know enough about git or svn or SCM systems in
general to identify the best way to go about doing this, but i have a
feeling that someone else on this list does.

so please comment: what is the best way to put the header files that
define the JACK API, along with the source code for the
example+utility clients somewhere that any implementation of the API
could use them?
PrevNext  Index

1326285794.26703_0.ltw:2,a <CAFa_cKmeL045fa=Eb7=H71Hu3OiiXuVszLCfGVa5HkSCSCYBiQ at mail dot gmail dot com>