Jack headers

classic Classic list List threaded Threaded
2 messages Options
ABL
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Jack headers

ABL
Hi all,
I have one question about the Jack dependency. As I see in the Windows build, only the headers inside the includes\jack folder are needed for the compilation of MuseScore (I tried to delete everything else of Jack folder: the build completed and the executable was able to talk with Jack). Is then possible to include these headers into MuseScore source code, so that it would be no more necessary to install Jack for MuseScore compilation?
The headers are these: JACK API headers https://github.com/jackaudio/headers
(Would Jack license enable such integration?)
I tried with the new headers from the GitHub repository as well as those shipped by Jack installation and I see no difference in the interplay between MuseScore and Jack on Windows (but actually I have no experience with Jack-audio and I did not test the executable extensively).
I am asking this because I am trying to enable a msys2 compilation of MuseScore and all the other dependencies needed by MuseScore can be obtained as pre-built binaries (and headers) through msys2 pacman instruction except for Jack. See here: https://github.com/AntonioBL/MuseScore/commit/fc7cd8bb608
and Appveyor log: https://ci.appveyor.com/project/AntonioBL/musescore/build/1.0.62

This could in principle also make much easier a 64bit Windows compile of MuseScore by using msys2, since all 64bit binaries would be already available.
(and possibly also a static build of MuseScore)

(There are some drawbacks: Qt5.6 shipped by msys2 depends on a larger number of dlls than the official one, the same holds for ogg/vorbis, see: https://github.com/AntonioBL/MuseScore/blob/fc7cd8bb608574342e8ef407b7413504faf791ae/mscore/CMakeLists.txt#L501-L517 and also portaudio from msys2 does not have ASIO but only MME, Windows DirectSound and Windows WDM-KS, instead of MME, Windows DirectSound, ASIO and skeleton implementation as it is now for MuseScore 2.0.3)

What do you think? Would it break something in the other OS (Linux, Mac)?

Ciao,
ABL
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Jack headers

lasconic
Administrator
I think it would be fine in the current code.

However, I'm a bit worried about going full msys2, especially with the drawbacks you mentioned. Current nightlies are built with a known set of dependencies and we know they work (like the old portaudio dll). If we use a package manager, we will need to make sure that we can control the versions that we packaged and of course that we don't get regressions in features.

lasconic

2016-05-06 14:27 GMT+02:00 ABL <[hidden email]>:
Hi all,
I have one question about the Jack dependency. As I see in the Windows
build, only the headers inside the includes\jack folder are needed for the
compilation of MuseScore (I tried to delete everything else of Jack folder:
the build completed and the executable was able to talk with Jack). Is then
possible to include these headers into MuseScore source code, so that it
would be no more necessary to install Jack for MuseScore compilation?
The headers are these: JACK API headers https://github.com/jackaudio/headers
(Would Jack license enable such integration?)
I tried with the new headers from the GitHub repository as well as those
shipped by Jack installation and I see no difference in the interplay
between MuseScore and Jack on Windows (but actually I have no experience
with Jack-audio and I did not test the executable extensively).
I am asking this because I am trying to enable a msys2 compilation of
MuseScore and all the other dependencies needed by MuseScore can be obtained
as pre-built binaries (and headers) through msys2 pacman instruction except
for Jack. See here:
https://github.com/AntonioBL/MuseScore/commit/fc7cd8bb608
and Appveyor log:
https://ci.appveyor.com/project/AntonioBL/musescore/build/1.0.62

This could in principle also make much easier a 64bit Windows compile of
MuseScore by using msys2, since all 64bit binaries would be already
available.
(and possibly also a static build of MuseScore)

(There are some drawbacks: Qt5.6 shipped by msys2 depends on a larger number
of dlls than the official one, the same holds for ogg/vorbis, see:
https://github.com/AntonioBL/MuseScore/blob/fc7cd8bb608574342e8ef407b7413504faf791ae/mscore/CMakeLists.txt#L501-L517
and also portaudio from msys2 does not have ASIO but only MME, Windows
DirectSound and Windows WDM-KS, instead of MME, Windows DirectSound, ASIO
and skeleton implementation as it is now for MuseScore 2.0.3)

What do you think? Would it break something in the other OS (Linux, Mac)?

Ciao,
ABL



--
View this message in context: http://dev-list.musescore.org/Jack-headers-tp7579896.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer
Loading...