[openal] Building with MinGW...?

[Mark Sibly]

Thanks Chris, using mingw-w64 did the trick. I almost had it going with
mingw-w32, but ran into dsound.h issues so gave up. mingw-w64 also fixed
some problems I was having with missing c++11 std features...

Quick question re: mingw-64 though: when I installed it, it had a combo box
for 'architecture' - i686 or x86_64.

What do they mean here exactly? Is this what the 64 compilers can 'build'
for? I selected i686, so does that mean I'm running 64bit compilers that
generate 32bit exes?

If so, I take it this is correct for OpenAL32?







On Fri, May 30, 2014 at 1:55 PM, Chris Robinson <chris.kcat at gmail.com>
wrote:

> On 05/29/2014 06:16 PM, Mark Sibly wrote:
>
>> Hi,
>>
>> I'm trying to build the latest openal-soft from git with MinGW 4.8.1, but
>> aren't having much luck.
>>
>> I tried:
>>
>>  cd build
>>> cmake -G "MinGW Makefiles" ..
>>> mingw32-make all
>>>
>>
>> Which generates a bunch of compiler warnings/errors such as:
>>
>> D:/openal-soft/include/threads.h:47:52: warning: 'struct timespec'
>> declared
>> inside parameter list [enabled by default]
>>   int althrd_sleep(const struct timespec *ts, struct timespec *rem);
>>
>
> Are you using mingw32 or mingw-w64? It works for me with mingw-w64, and
> mingw32's headers are known for missing things, so if you're using mingw32
> it could be missing the timespec struct.
>
> I can change the check in threads.h to _TIMESPEC_DEFINED, which is what my
> mingw-w64 headers define when declaring the timespec struct, though I don't
> know if other Windows compilers that have timespec will also set that.
> _______________________________________________
> openal mailing list
> openal at openal.org
> http://openal.org/mailman/listinfo/openal
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openal.org/pipermail/openal/attachments/20140531/d79852fb/attachment.html>