Hi,
When compiling Pd vanilla even if the configure script picks the jack dependencies confirmed by:
JACK ........................ yes
Pd is not compiled with jack support.
It is only if ./configure --enable-jack is explicitly added.
Shouldn't the configure output reflect if jack support is going to be added or not?
No big deal, but just wondering. Lorenzo.
On 03/25/2015 10:00 PM, Lorenzo Sutton wrote:
Hi,
When compiling Pd vanilla even if the configure script picks the jack dependencies confirmed by:
JACK ........................ yes
Pd is not compiled with jack support.
It is only if ./configure --enable-jack is explicitly added.
Shouldn't the configure output reflect if jack support is going to be added or not?
it does, but you are confused because Pd's configure (the one which requires the "--enable-jack" option) calls portaudio's configure (which in turn prints "JACK.......yes").
since you are building Pd with portaudio support, you will get jack support as indicated, but via portaudio, not natively (which requires "--enable-jack")
gfmsdr IOhannes
On 25/03/2015 22:41, IOhannes m zmölnig wrote:
On 03/25/2015 10:00 PM, Lorenzo Sutton wrote:
Hi,
When compiling Pd vanilla even if the configure script picks the jack dependencies confirmed by:
JACK ........................ yes
Pd is not compiled with jack support.
It is only if ./configure --enable-jack is explicitly added.
Shouldn't the configure output reflect if jack support is going to be added or not?
it does, but you are confused because Pd's configure (the one which requires the "--enable-jack" option) calls portaudio's configure (which in turn prints "JACK.......yes").
since you are building Pd with portaudio support, you will get jack support as indicated, but via portaudio, not natively (which requires "--enable-jack")
Ah, ok. now it's clear! Thanks for the explanation.
Lorenzo.
-
IOhannes m zmölnig -
Lorenzo Sutton