ALSA Dependency - Is it necessary?
Andrew John Hughes
gnu_andrew at member.fsf.org
Sun Feb 10 14:27:38 PST 2008
On 10/02/2008, Michael Franz <mvfranz at gmail.com> wrote:
> > You could patch IcedTea to not use ALSA. It's some boring work of
> > compile, remove, recompile, re-remove... but in the end, it's just to
> > erase any native file that uses it for now. One example of code that
> > make use of ALSA for sure is the Sound API.
> > Let me know if you need help (I don't have access to a Mac and not much
> > free time though).
> > Mario
> The first step that would be appreciated would be a way to turn of the check
> for ALSA in configure. Due to the way I am building this (via macports) I
> have to manually remove the ALSA check in configure.ac then run autoconf and
> then configure. If I could just pass --disable-alsa my process would be
> I initially started using icedtea 1.5 and am not using a snapshop of head.
This is only possible to do easily if the OpenJDK build underlying
IcedTea actually supports a DISABLE_ALSA option. Although you can add
--disable-alsa to autoconf easily enough on IcedTea, the actual ALSA
requirement comes from OpenJDK which doesn't the autotools but rather
a series of Makefiles. You'd need support in these Makefiles to be
able to disable ALSA (a DISABLE_ALSA build variable just like BOOTDIR
and the rest). If that doesn't exist, it's a case of going through
the Makefiles manually and adding such support.
That said, I guess there will be other problems with the OpenJDK build
given it hasn't been tested on or ported to Mac OS X. Getting past
IcedTea's configure is only the beginning.
Support Free Java!
Contribute to GNU Classpath and the OpenJDK
More information about the distro-pkg-dev