[Openal] Dev C++
gerth at ucalgary.ca
Wed Jan 4 09:58:28 PST 2006
Allow me to clarify my woes,...I've already posted a kluge/workaround
on this mail list and on my blog
I was trying to compile working applications from sample code using Dev
Absolutely none of the (english) samples available on the links at
OpenAL.org compiled, straight off.
Most worked If I use MS-VStudio. Examples that are supposed to work
with Dev C++ project files do not compile.
Fixing the include & lib directories, adding compiler options doesn't
fix the Dev C++ tutorials on DevMaster.net.
(I got them to compile, but they didn't play sounds....yes I made sure
the dll was around, the binary exe that compiled was considerably
smaller than the binary that works and comes with the "sample/source"
Importing the MS-VStudio examples that come with OpenAL SDK and then
Doing the above(if needed) doesn't work.
Doing the above with the samples from:
I would like to contribute by atleast getting the samples in the OpenAL
SDK working with Dev C++ (in the same fashion as above) but
unfortunately the use of Framework.h and associated problems with the
compiler are one level of convolution to much for my puny brain. I would
make an updated example for Dev C++, if I could figure stop the compiler
Warning: .drectve `/DEFAULTLIB:"uuid.lib" /DEFAULTLIB:"uuid.lib" '
It is somehow related to these compiler options/libraries...duh
That being said, I am glad the kluge I discovered works, and hope
future OpenAL changes don't break it.
Sven Panne wrote:
>I am not exactly sure what you are trying to do: Compile OpenAL itself
>from CVS or simply use an existing OpenAL implementation? For the latter
>I would just grab the binary OpenAL SDK from www.openal.org and set up
>some paths in the development environment to use it.
>Compiling the "portable" CVS module itself under Windows is a different
>story: In theory it might work, but I fear that the Windows backend
>might have bitrotted because of the lack of a maintainer. The brave
>might try a Cygwin or MinGW/MSYS build or even setup a VisualStudio
>project, but expect some minor problems. I'd be interested to hear about
>problems, fixes, etc., as I have currently very little time to do this.
>If somebody would like to take the task of the "official" Windows
>maintainer, even better.
>In general, we need some more people working on the "portable" module,
>currently we are only 2-3 people, which is not very much. There is a
>large range of tasks which could be taken by someone, e.g. maintaining a
>specific backend, implementing the 1.1 queueing mechanism, doing the
>packaging for a platform (Fedora, SuSE, *BSD, Windows, ...), improving
>performance, etc. So if you'd like to participate, please feel free to
>mail to openal-devel at opensource.creative.com.
>>From: openal-admin at opensource.creative.com
>>[mailto:openal-admin at opensource.creative.com] On Behalf Of
>>Sent: Dienstag, 3. Januar 2006 20:08
>>To: openal at opensource.creative.com
>>Subject: [Openal] Dev C++
>>It appears to me that OpenAL is experiencing some serious
>>issues, but I'm just getting started with OpenAL.
>>I haven't tried using anything from CVS,...yet.
>>I haven't been able to build any applications using openAL. I
>>am using Dev C++.
>>The tutorials on DevMaster don't build...however the binaries
>>I've tried fixing the obvious mistakes, and even imported the
>>MSVisStudio Projects, but everything has failed to compile. I
>>suspect the problem is with Alut, but various combinations of
>>the different versions available hasn't yielded any success.
>>I am using 22.214.171.124 of Dev C++, if you can build with OpenAL
>>in Dev C++, I'd like to hear what is needed.
>openal mailing list
>openal at opensource.creative.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openal