Hello,
Sorry for the late reply, it took a while to try these things out ..
Please find my remarks in line.
> -----Original Message-----
> From: oss-devel-boun...@mailman.opensound.com
> [mailto:oss-devel-boun...@mailman.opensound.com] On Behalf Of Yair K.
> Sent: 04 February, 2011 20:37
> To: oss-devel@mailman.opensound.com
> Subject: Re: [oss-devel] OSS4 for embedded targets
>
> On Thursday 03 February 2011 16:52:20
> sven.bieb...@be.thalesgroup.com wrote:
> > Hello,
> >
> > Having decided to use 2.6 on my embedded target, I am
> running into a
> > few problems that require code/script changes. Hence my
> post in this
> > channel and not the general support.
> >
> > I am more than willing to provide the changes should they appeal ...
>
> The build system is messy. If you have anything useful I'm
> sure the list would like to see it.
I can see what you mean now ...
As soon as I figure all the details out, I will make a new topic on this
list.
>
> > The following issues arose:
> > * building libsalsa requires libtool to support --tag,
> older libtool
> > versions do not support it yet.
>
> I wonder if libtool is really necessary for it to build. No matter...
>
> > The existence of libtool and/or its support for the
> parameter could
> > be checked by the configure script, which could then bail
> and suggest
> > the user to use --enable-libsalsa=NO.
A patch is attached for the configure script that does just that.
For the --tag support I still need to dig a bit further.
> > * the ogg vorbis support is checked in two directories,
> however, the
> > #include statement is formed so it only fits one of both, causing a
> > compile error when in the other case.
>
> The include statement is <vorbis/vorbisfile.h>. Perhaps
> utils/ossmkdep.h should just add the /usr/local/include directory?
>
> > * the graphical tools require gtk support, however the
> configure does
> > not check for its presence, nor can they be disabled by the
> configure.
>
> They are tested later (setup/setupdir.sh, setup/srcconf.c).
> Yea, adding a disable switch would be useful. I can send a
> diff if anyone is interested.
Yes please, that would be very useful
> >
> > More issues come from the actual installation on my
> linker-less target... .
> > The modules cannot be installed on target via
> tarball/soundon but they
> > cannot be created on the host via "make install" without
> affecting my
> > host setup.
> >
> > Can you provide me with pointers how to add support for
> specifying an
> > install root, so OSS can be deployed in a temporary location ? This
> > allows making a root file system that be dumped on my
> target and does
> > not need manual adaptations afterwards.
>
> You can edit setup/Linux/make.local to add a target.
I added a remote_install option that passes a directory to install.sh. When
the directory is not specified (as in the normal "make install" or via
soundon ), the install.sh falls back to the default "/".
This morning however, I thought of an alternative, namely to specify this at
configure time. This allows the procedure to be the same,
but requires all scripts to be adapted. OTH, specifying it at the make,
allows the same oss to be installed both on host and on target, although I
do not know if this is useful : on embedded targets the kernel is often
different and most of the time you want explicit control, which means from
the configure stage onwards different parameters passed and a separate build
directory.
What would fit OSS best ?
Thanks in advance,
Sven
*** oss-v4.2-build2004-src-gpl/configure 2011-01-05 02:33:07.000000000
+0100
--- configure 2011-02-08 14:46:44.867728000 +0100
*************** case `uname` in
*** 227,232 ****
--- 227,239 ----
if test "$NOALSA" != "1"
then
+ if test "`which libtool 2>/dev/null` " = " "
+ then
+ echo "Libtool cannot be found on your system. If you
need the alsa simulation,"
+ echo "please install it or use --enable-libsalsa=NO to
disable the alsa simulation."
+ exit 1;
+ fi
+
if test -d /usr/include/alsa || test -d /usr/local/include/alsa
then
echo Compiling libsalsa library
_______________________________________________
oss-devel mailing list
oss-devel@mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel
