2 Feb
2009
2 Feb
'09
7:45 p.m.
Hi all,
I'd like to experiment with LASH, toward incorporating LASH
client functionality into Nama.
I could use a little help getting LASH to compile,
Lash-audio.org seems to be down. Perhaps someone here
knows what to do.
After some fiddling under my debian/sid distribution, I
start with configure thusly:
XML_LIBS=/usr/lib JACK_LIBS=/usr/lib READLINE_LIBS=/usr/lib/libreadline.so
JACK_CFLAGS=-I/usr/include ./configure
(Configure and its brethren seem to expect to find libs and
includes under /usr/local.)
Right now the problem is in compiling simple_client.c:
gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. /usr/include/ -I/usr/include/alsa -g -O2 -MT
lash_simple_client-simple_client.o -MD -MP -MF .deps/lash_simple_client-simple_client.Tpo
-c -o lash_simple_client-simple_client.o `test -f 'simple_client.c' || echo
'./'`simple_client.c
simple_client.c: In function 'main':
simple_client.c:95: error: 'JackNullOption' undeclared (first use in this
function)
I see JackNullOption is defined in /usr/include/jack/types.h,
so I tried adding this line to simple_client.c:
#include <jack/types.h>
and later
#include </usr/include/jack/types.h>
Still getting the same error.
Could there be a JACK version problem? LASH expects
jack_version > 0.99, but the latest JACK I have is 0.116.
I had just hacked that part:
MISSING_REQUIRED=" JACK >= 0.1"
Any suggestions or explanations by the C-savvy would be welcome.
Joel
--
Joel Roth
2 Feb
2 Feb
8:53 p.m.
There's no problem with compilation. If any, it'd be distro-specific
(dependencies, needed *-devel files if any, version mismatch etc). Run
configure with a prefix:
./configure --prefix=/usr
The following are known dependencies:
dbus
gtk2
jack
libxml2
python
10:14 p.m.
On Tue, Feb 03, 2009 at 08:53:44AM +0800, Ray Rashif wrote:
There's no problem with compilation. If any,
it'd be distro-specific
(dependencies, needed *-devel files if any, version mismatch etc). Run
configure with a prefix:
./configure --prefix=/usr
I see that takes care of most of the headers:
$includedir=${prefix}/include
However, I still get the same error as before:
gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I/usr/local/include -I/usr/include/alsa -g
-O2 -MT lash_simple_client-simple_client.o -MD -MP -MF
.deps/lash_simple_client-simple_client.Tpo -c -o lash_simple_client-simple_client.o `test
-f 'simple_client.c' || echo './'`simple_client.c
simple_client.c: In function 'main':
simple_client.c:94: error: 'JackNullOption' undeclared (first use in this
function)
Shouldn't there be an '-I/usr/include' appearing above?
Also what is the standard way to exclude simple_client
from compiling?
The following are known dependencies:
dbus
gtk2
jack
libxml2
python
I have all of these.
Thanks.
Joel
--
Joel Roth
3 Feb
3 Feb
12:19 a.m.
Shouldn't there be an '-I/usr/include'
appearing above?
Yes, there should be nothing "local" in the Makefile if you do a search.
Most probably pkg-config isn't right, but this should not happen in Debian.
Paths aren't the problem here, though. Try:
./configure --prefix=/usr \
--without-jack-dbus
I've read there's a problem with jack1+dbus. Sorry I can't be of more
qualified help, but an e-mail to a Debian package maintainer, lash and jack
dev will definitely shed light.
3:47 a.m.
Ray Rashif <schivmeister(a)gmail.com> writes:
LASH using jack1+dbus is indeed not good combination. But I doubt the
compilation problem is related to this.
Joel Roth <joelz(a)pobox.com> wrote:
Shouldn't
there be an '-I/usr/include' appearing above?
Yes, there should be nothing "local" in the Makefile if you do a search.
Most probably pkg-config isn't right, but this should not happen in Debian.
Paths aren't the problem here, though. Try:
./configure --prefix=/usr \
--without-jack-dbus
I've read there's a problem with jack1+dbus. Sorry I can't be of more
qualified help, but an e-mail to a Debian package maintainer, lash and jack
dev will definitely shed light. Could there be a JACK version problem? LASH expects
jack_version > 0.99, but the latest JACK I have is 0.116.
I had just hacked that part:
MISSING_REQUIRED=" JACK >= 0.1"
So you disabled a check against jack2. I think lash was working with
jack1 in dbus-less mode but I havent tested it much.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
5:22 a.m.
On Tue, Feb 03, 2009 at 09:47:47AM +0200, Nedko Arnaudov wrote:
Ray Rashif <schivmeister(a)gmail.com> writes:
>> Shouldn't there be an '-I/usr/include' appearing above?
>
> Yes, there should be nothing "local" in the Makefile if you do a search.
> Most probably pkg-config isn't right, but this should not happen in Debian.
> Paths aren't the problem here, though. Try:
>
> ./configure --prefix=/usr \
> --without-jack-dbus
>
> I've read there's a problem with jack1+dbus. Sorry I can't be of more
> qualified help, but an e-mail to a Debian package maintainer, lash and jack
> dev will definitely shed light.
LASH using jack1+dbus is indeed not good combination.
But I doubt the
compilation problem is related to this.
Joel Roth <joelz(a)pobox.com> wrote:
I see that I came late to the party. I didn't know about
jack2 or jack1.
The JACK website makes no mention of jack2. However I have
found your pages, enough to get an inkling of the issues
involved. Looking at the LASH manual I thought I might be
able to get access to the LASH dynamic library for an
application written in perl. Might make more sense to
start with an older version of LASH.
Thanks for taking the time to reply.
Could there be a JACK version problem? LASH
expects
jack_version > 0.99, but the latest JACK I have is 0.116.
I had just hacked that part:
MISSING_REQUIRED=" JACK >= 0.1"
So you disabled a check against jack2. I think lash was working with
jack1 in dbus-less mode but I havent tested it much. --
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
--
Joel Roth
11:55 a.m.
Joel Roth <joelz(a)pobox.com> writes:
Looking at the LASH manual I thought I might be
able to get access to the LASH dynamic library for an
application written in perl. Might make more sense to
start with an older version of LASH.
I've made Python SWIG bindings for LASH and probably it will be trivial
to generate perl bindings. The only problem I had was because of the
compex argv in/out parameter used in lash initialization. But IIRC argv
is not used anymore in 0.6.0 - environment variable is used instead.
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
2:42 p.m.
On Tue, Feb 03, 2009 at 05:55:41PM +0200, Nedko Arnaudov wrote:
Joel Roth <joelz(a)pobox.com> writes:
I've only just read my first C tutorials to understand what
all those * mean in the function definitions. I didn't get
as far as ** and ***. If you've got SWIG bindings, that
might help me, as SWIG works for Perl, too.
Another, bindings option for perl, Inline::C, also
offers a fairly straightforward way to use dynamic
libraries.
http://search.cpan.org/~sisyphus/Inline-0.45/C/C-Cookbook.pod
So one way or another, I think it should be possible to
better integrate Ecasound, via the track and bus abstracts
provided by Nama, with the rest of the JACK ecosystem.
Looking at the LASH manual I thought I might be
able to get access to the LASH dynamic library for an
application written in perl. Might make more sense to
start with an older version of LASH.
I've made Python SWIG bindings for LASH and probably it will be trivial
to generate perl bindings. The only problem I had was because of the
compex argv in/out parameter used in lash initialization. But IIRC argv
is not used anymore in 0.6.0 - environment variable is used instead. --
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
--
Joel Roth
5995
days inactive
5996
days old
linux-audio-user@lists.linuxaudio.org
7 comments
3 participants
participants (3)
-
Joel Roth -
Nedko Arnaudov -
Ray Rashif