[alsa-devel] Installing a "different" version of Alsa
Hello,
It's been a year since I posted to this list, but I'm running into a problem and can't figure out the best way to solve it, so I'm hoping someone here can help.
I've got an SDK for an embedded platform that includes a specific version of Linux with ALSA built-in. On my platform, I want to use a different (newer) version of ALSA than the built-in version, so I want to build and load the binaries from the newer version and, more importantly, I want to compile my custom sound hardware driver against the newer alsa version and the SDK's Linux version. I don't really want to touch the kernel files that are in the kerenl/include/sound directory in the SDK.
When I use kbuild to build my custom sound hardware driver against the SDK in the kernel, it always trys to pick up the older ALSA header files that are in the SDK, but I want to use the newer versions that are in the directory with the newer version of ALSA. What the best way to make sure I get the correct headers? Is what I'm trying "dangerous" and should I be going about this a different way?
Thanks for any advice,
Brian
On Sat, Dec 19, 2009 at 09:48:16PM -0700, Brian Welch wrote:
[Please fix your MUA to word wrap lines at ~80 columns, it would make your mails much easier to read.]
When I use kbuild to build my custom sound hardware driver against the SDK in the kernel, it always trys to pick up the older ALSA header files that are in the SDK, but I want to use the newer versions that are in the directory with the newer version of ALSA. What the best way to make sure I get the correct headers? Is what I'm trying "dangerous" and should I be going about this a different way?
The best way of integrating with the toolchain you're using will usually depend on the toolchain - you'll generally be able to get better advice about how to work with the toolchain by asking people who work with the toolchain.
participants (2)
-
Brian Welch
-
Mark Brown