[Openal] Header files placement
garinh at cheesetoast.net
Tue Aug 15 10:47:33 PDT 2006
> Could someone come with strong arguments why OpenAL wont use <AL/al.h> under
> windows instead of <al.h> or "al.h"
> The SDK installation assumes that this is the case, why?
The decision was made to go this way because Windows-centric programmers
are used to this kind of setup, and Windows-centric developers are the
target developer for the Creative OpenAL SDK.
I agree that it's a nuisance for cross-platform development, but the
issue can be addressed by manually copying the headers to the desired
location(s), environment variables, or other methods.
> Makes life a mess to do cross-platform compilation, which is the main reason
> for using OpenAL in the first place, right?
OpenAL is of course very strong for cross-platform work, but that is not
the primary reason _Creative_ has pushed OpenAL. We promote OpenAL as a
hardware-accelerated audio path for Windows gaming applications
(although that strategy will be modified a bit next year when we'll have
an accelerated path on Linux as well).
For better or for worse, that's the scoop...
More information about the Openal