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.

> 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.
> * 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.

> 
> 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.

Yours,
        Yair K.
_______________________________________________
oss-devel mailing list
oss-devel@mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel

Reply via email to