OpenAL Soft 1.15.1 is out

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

gouessej
Administrator
It works, I've just tested TUER under Windows 7 64 bits, soft_oal.dll is correctly loaded.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

Xerxes Rånby
In reply to this post by Sven Gothel
Sven Gothel wrote
On 03/23/2013 12:39 PM, gouessej [via jogamp] wrote:
> Sven, do you like this solution?
> http://tuer.svn.sourceforge.net/viewvc/tuer/pre_beta/build.xml?r1=657&r2=658
>
> I download the ZIP containing OpenAL-Soft binaries for Windows, I extract the
> useful DLLs, I put them into JOAL JARs and I clean up my mess. I just hope
> they don't depend on msvcrt.

As a manual binary blob update for windows - YES, that is great.
Then you could update the blob in the repo!

But I would not like to do this at build time,
i.e. injecting untested binary blobs.

So .. as a ant recipe for manual use, test and git commit - cool.
A good remedy until we know how to do it right on Windows.
I agree, the aim for JogAmp JOAL native builds is to only ship binary’s what we can produce our-self using free software tool-chains when possible.

For the record, newdawnsoftware who maintaints the LWJGL build farm build their openal-soft natives using the microsoft visual studio 9 compiler.
http://ci.newdawnsoftware.com/job/OpenAL-win32/1284/console
http://ci.newdawnsoftware.com/job/OpenAL-win64/1281/console








Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

gouessej
Administrator
Xerxes Rånby wrote
For the record, newdawnsoftware who maintaints the LWJGL build farm build their openal-soft natives using the microsoft visual studio 9 compiler.
http://ci.newdawnsoftware.com/job/OpenAL-win32/1284/console
http://ci.newdawnsoftware.com/job/OpenAL-win64/1281/console
Maybe we can do the same thing without MS VS 9.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

Sven Gothel
Administrator
In reply to this post by Xerxes Rånby
On 03/25/2013 01:41 PM, Xerxes Rånby [via jogamp] wrote:

>     Sven Gothel wrote
>     On 03/23/2013 12:39 PM, gouessej [via jogamp] wrote:
>     > Sven, do you like this solution?
>     > http://tuer.svn.sourceforge.net/viewvc/tuer/pre_beta/build.xml?r1=657&r2=658
>     >
>     > I download the ZIP containing OpenAL-Soft binaries for Windows, I
>     extract the
>     > useful DLLs, I put them into JOAL JARs and I clean up my mess. I just hope
>     > they don't depend on msvcrt.
>
>     As a manual binary blob update for windows - YES, that is great.
>     Then you could update the blob in the repo!
>
>     But I would not like to do this at build time,
>     i.e. injecting untested binary blobs.
>
>     So .. as a ant recipe for manual use, test and git commit - cool.
>     A good remedy until we know how to do it right on Windows.
>
> I agree, the aim for JogAmp JOAL native builds is to only ship binary’s what
> we can produce our-self using free software tool-chains when possible.
_when possible_

until that day, I would love to see Juliens ant targets in JOAL
and us providing the openal-soft dlls, allowing folks to use JOAL on Windows :)

Can we do this ?

~Sven



signature.asc (911 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

gouessej
Administrator
Do you want this target to be called when building JOAL or should it be kept apart?
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

Sven Gothel
Administrator
On 03/26/2013 09:55 AM, gouessej [via jogamp] wrote:
> Do you want this target to be called when building JOAL or should it be kept
> apart?

apart, i.e. so we can call it manually for initial windows DLL 'injection'
and later updates.

I would like to see 2 commits, 1st your new ant target to download and extract
to the 'proper place' for being picked up by our archiving target.

2nd: After you manually executed it for 32bit and 64bit windows,
i.e. pushing the soft-openal DLL files.

Again - this is a workaround until we can build it,
but it will enable the Windows platform again.

~Sven



signature.asc (911 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

Sven Gothel
Administrator
In reply to this post by gouessej
On 03/26/2013 09:55 AM, gouessej [via jogamp] wrote:
> Do you want this target to be called when building JOAL or should it be kept
> apart?

apart, i.e. so we can call it manually for initial windows DLL 'injection'
and later updates.

I would like to see 2 commits, 1st your new ant target to download and extract
to the 'proper place' for being picked up by our archiving target.

2nd: After you manually executed it for 32bit and 64bit windows,
i.e. pushing the soft-openal DLL files.

Again - this is a workaround until we can build it,
but it will enable the Windows platform again.

~Sven



signature.asc (911 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

gouessej
Administrator
In reply to this post by Sven Gothel
If I put soft_oal.dll files into the right directories manually with the first target, there will be nothing else to do (except if you prefer having a second target that injects them into the both JARs for 32 & 64 bits). Ok I will modify my Ant target so that it copies the DLLs into the both directories indicated by Xerxes (joal/make/lib/windows-i586 and joal/make/lib/windows-amd64). I can make another pull request during this night.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|

Re: OpenAL Soft 1.15.1 is out

gouessej
Administrator
In reply to this post by Sven Gothel
12