[Nix-dev] Re: *** GMX Spamverdacht *** Re: *** GMX Spamverdacht *** Re: alsaib patch 2snd part

[Eelco Dolstra]

Hi,

Marc Weber wrote:

>> I don’t think anything like that is needed: $ALSA_PLUGINS_DIR is read by
>> alsa-lib, which allows it to find ALSA plug-ins, even those installed in
>> the user environment.  That’s all we need, right?
> consider an x86_64 system. Now intall i686 Skype
> Which alsaPlugins to should be insalled now?  the i686 or the x86_64
> version?

One solution may be to store plugins in the <arch> subdirectory of each
directory in $ALSA_PLUGINS_DIR.  E.g. when building the 64-bit plugin, you put
it under $out/lib/x86_64/plugin.so, and on 32-bit under $out/lib/i686/plugin.so.
  Then stick the 32-bit and 64-bit plugins in $ALSA_PLUGINS_DIR and voila.  The
Glibc dynamic linker does something like that.

Alternatively, have the plugin loader try the remaining paths in
ALSA_PLUGINS_DIR if dlopen() fails.  Then it will just skip plugins for the
wrong architecture.

Anyway, it seems that there are simpler solutions than introducing wrappers
everywhere.

-- 
Eelco Dolstra | http://www.st.ewi.tudelft.nl/~dolstra/