Why is the Mac Open AL framework being loaded dynamically?
by Chris Dillman · in Torque Game Builder · 04/13/2005 (6:42 pm) · 6 replies
Why is the Mac Open AL framework being loaded dynamically?
Im looking over the code and think it should just be linked in non dynamically from System/Library etc.
This should make it so that Open AL frame work will load and link any other mac framework. Meaning it should be found and loaded at run time automatically from any of the normal framework search paths....
Which I think includes
Bundle/frameworks as a default...
Which would help solve the common issue I see about distributing the Open AL framework with the applications.
Im looking over the code and think it should just be linked in non dynamically from System/Library etc.
This should make it so that Open AL frame work will load and link any other mac framework. Meaning it should be found and loaded at run time automatically from any of the normal framework search paths....
Which I think includes
Bundle/frameworks as a default...
Which would help solve the common issue I see about distributing the Open AL framework with the applications.
#2
Here is some quicky-type code I wrote to get embedded OpenAL frameworks working with TGE. Just compile your app as usual, add the OpenAL framework bundle inside of it, and you're set to go.
It's on my to-do list to test this rigorously and then submit it as an official patch.
04/13/2005 (8:30 pm)
Yes, as David mentions I believe this is a licensing deal.Here is some quicky-type code I wrote to get embedded OpenAL frameworks working with TGE. Just compile your app as usual, add the OpenAL framework bundle inside of it, and you're set to go.
It's on my to-do list to test this rigorously and then submit it as an official patch.
#3
How does this avoid violating OpenAL's LGPL?
04/13/2005 (8:47 pm)
Quote:Here is some quicky-type code I wrote to get embedded OpenAL frameworks working with TGE.
How does this avoid violating OpenAL's LGPL?
#4
Some of GG games work this way, therefore it must be license compliant. I don't see how this could be considered any different than, say, distributing LGPLCODE.DLL with your application under Windows. It should be completely within section 5 of the LGPL.
04/13/2005 (8:50 pm)
It's still a dynamically loaded framework. (Delete the "OpenAL" directory from the app bundle's framework directory and the T2D program still runs.)Some of GG games work this way, therefore it must be license compliant. I don't see how this could be considered any different than, say, distributing LGPLCODE.DLL with your application under Windows. It should be completely within section 5 of the LGPL.
#5
04/14/2005 (10:56 am)
TGE itself will be moving to linking to OpenAL as David suggests in the next update, and at that time, T2D will as well.
#6
1.
> David Blake
The default method of adding a Framework to Xcode or CW is
to simply drag it into your project.
This set its as a dynamicalling linked lib.
You really have to try to make it static.
2.
Open AL officially ships on Tiger 10.4 as a standard framwork.
3. As I was saying I think the default search paths for linked in frameworks are....
Bundle/frameworks
User/library/framworks
System/library/frameworks
I think they are searched in that order.
Any how my point is that the Mac code is specifically loading the Open AL framework using code. Instead of just linking to it in teh project and having the OS load the framework in the normal method.
So Im wondering why that is being done?
04/14/2005 (11:37 am)
Pardon my spelling I have no way to check it at this location.1.
> David Blake
The default method of adding a Framework to Xcode or CW is
to simply drag it into your project.
This set its as a dynamicalling linked lib.
You really have to try to make it static.
2.
Open AL officially ships on Tiger 10.4 as a standard framwork.
3. As I was saying I think the default search paths for linked in frameworks are....
Bundle/frameworks
User/library/framworks
System/library/frameworks
I think they are searched in that order.
Any how my point is that the Mac code is specifically loading the Open AL framework using code. Instead of just linking to it in teh project and having the OS load the framework in the normal method.
So Im wondering why that is being done?
Associate David Montgomery-Blake
David MontgomeryBlake