Since you mentioned this, how about adopt current OS X bundle structure as default GNUstep structure? The pro of this is that OS X bundle actually can allow multiple platforms of binaries coexist in a single wrapper. OS X used Contents/MacOS (and a fat Mach-O binary may reside in it) as the folder where the binary exists, while GNUstep can use something like Contents/GNUstep-i386-linux-gnu for i386 and Contents/GNUstep-x86_64-linux-unknown for amd64 (as neither ELF for Linux nor COFF/PE for Windows can do fat binaries). This will allow distributing a single bundle with one copy of resources while supporting multiple platforms.
发自我的 iPad 在 2013-5-22，16:52，Luboš Doležel <[email protected]> 写道： >>> Both those changes sound reasonable to me, as long as they are clearly >>> commented so that someone (like me) doesn't come along later and, >>> forgetting what they are for, remove them because the look unneccessary. > > Hi, > > the patch is attached for your review and inclusion. > > I ran make check, which produced an issue which I then fixed, so some testing > was involved. > I may possibly come up with more patches, but this should get me started. > > Thanks! > -- > Luboš Doležel > <nsbundle-extloader.patch> > _______________________________________________ > Gnustep-dev mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnustep-dev _______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
