Ok. I'm sending this message back to the mailing list in case it gives others 
ideas about the problem.

On Mar 1, 2010, at 08:59, Dominik Reichardt wrote:

> Am 01.03.2010 um 14:02 schrieb Ryan Schmidt:
> 
>>> 
>>> I'm struggling with building our game engine (Exult) statically, since we 
>>> want to have it ready for a possible release soon. After messing around 
>>> with the hurdles of building programs static, I had been almost successful, 
>>> only to be plagued by libsdl_mixer. It's static file is dynamic linked to 
>>> other libs (libvorbis, libogg, libflac) which IMHO defeats the purpose of 
>>> having a static lib.
>> 
>> That sounds like a valid complaint. For the benefit of those of us not 
>> familiar, how do you determine that the static lib is dynamically linked to 
>> other libs?
>> 
> 
> I have no real idea how to tell that. otool does not print out any dylib, 
> though when I look at libsdl_mixer.a directly, I see the references to the 
> dylib files. Also it was clear when Exult was running in the "Activity 
> Monitor.app" that the dylibs were used, even though Exult doesn't link them 
> and libsdl_mixer.a was linked in the exult binary.
> 
>> 
>>> I'm not sure if that is a ticketable issue or if there is any way to hack 
>>> around that static/dynamic issue that Apple produced.
>> 
>> Sounds like a valid thing to open a ticket for. Though the libsdl_mixer 
>> portfile doesn't appear to do anything special, so a plain from-source build 
>> outside of MacPorts would probably also exhibit this problem, so it's 
>> probably an upstream problem and should probably be reported there.
>> 
>> 
> 
> Yes, building directly from source was not successful as well, and I couldn't 
> "hack" the makefile similar to how I "hacked" the exult makefile to link to 
> the static libs :(
> So, this is most likely an upstream problem.
> 
>>> So, again, any way to hack the build of libsdl_mixer to link the libs 
>>> statically?
>> 
>> I have no idea how to fix this problem. Contacting the developers of this 
>> software may be your best bet.
> 
> 
> I'll try my best, though I fear I know the response already  (use the 
> precompiled framework!) :)
> 
> So, I'll open a ticket here and will contact the SDL devs on their forum/ML.
> 
> Thanks 
> --
> Take care
> Dominik Reichardt

_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to