Hi Dan, > If I recall correctly, a universal binary isn't actually a single file, it > is multiple executable files stored in side of an app bundle under > Contents/MacOS/ and then referenced in the Contents/Info.plist. I think the > first place to look is at the format of Info.plist for app bundles, that > should tell you some info on what meta is needed to consider something a > universal binary. Oh, and if that is the case, it would almost be pointless > becase an app bundle is specifically for when an application has a gui, > which would mean there is no point for swfmill. Hope this helps.
>From what I've read you can take the bundle approach if you are dealing with a GUI application and the one file route if you're building a command-line tool. I remember reading that they've fiddled with the ELF headers (or Mach headers, can't remember which) to make this work. Cheers, Steve -- Steve Webster http://dynamicflash.com _______________________________________________ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
