Activating assert() in the default error message handler isn't always
good for producitve systems. Make this optional and enable only when
a special configure option is given (i.e. for explicit debugging).
It's annoying that the configure script stops with an error if
python-config doesn't exist. It's no fatal error, so the configure
should disable the python components and continue.
reasons:
- rapid development
- class-like code structure
- more readable code
features:
- hcontrol binding is managed from python (opportunity to create
virtual mixer without driver or join multiple cards to behave as one)
Added --with-configdir and --with-plugindir options to configure
which specify the directories for config files and plugin objects
respectively. The default paths when these options are not
specified are unchanged.
Added --enable-symbolic-functions configure option. This will detect
and pass -Bsymbolic-functions linker option, which gives you better
performance and smaller binary size. Only recent binutils supports
this option.
- add long card name to device description
- create empty PCM plugin to allow right hint description parsing
- reorder devices in alsa.conf
- make namehint more configurable (using default.namehint.showall switch)
- add two levels basic and exteded for hints to default configuration files
- do not show direct device aliases
- removed all known memory leaks
the current configure script assumes that it will be run in the srcdir ... i
often build things out of tree so you can quickly punt all the generated
files:
mkdir build
cd build
../configure
cd ..
rm -r build
clean!
this tweaks the configure script in a few places to use the correct variable
instead of assuming that configure is always in $PWD ...
i say "sort of" in the subject because there is still the issues of the pcm
symbols list being generated in $builddir instead of $srcdir and the alsa
include symlink, but these doesnt really concern me for what i need ;)
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
See: bug#2274
checking for versioned symbols... ./configure: line 19347: test: "1: integer
expression expected
./configure: line 19350: test: "1: integer expression expected
This is caused by my libtool VERSION string:
VERSION="1.5.22 Debian 1.5.22-2"
The test in configure.in can't currently deal with the quotes.
From: Mike Frysinger <vapier@gentoo.org>
some architectures, like Blackfin, have a prefix added to all symbols (in our
case it's historical baggage)
while normally packages shouldnt care, when code starts mixing assembler with
C (like symbol versioning), you need to dip down into the inner details.
find attached a patch which queries gcc for the prefix (all gcc toolchains
have a builtin define of __USER_LABEL_PREFIX__) and then automatically has
asm() constructs utilize this
since most targets define __USER_LABEL_PREFIX__ to nothing, hopefully this
shouldnt cause any problems :)
Add configuration options to change the default device path from the
default /dev/snd. This is useful for embedded systems that do not want
subdirectories in /dev.
