What I meant is not to use links but a common filesystem layout, as I may need to transfer the bundles through formats that does not accept symlinks. Binaries are compiled and linked separately, while the resources are shared, so library issue can be spotted and hunted architecture by architecture.
发自我的 iPhone 在 2013-5-22，20:55，Niels Grewe <niels.gr...@halbordnung.de> 写道： > > On 22.05.2013 14:44CEST Chan Maxthon <xcvi...@me.com> wrote: > >> Including OS X? I mean I intend to compile a single bundle, with a single >> copy of all resources, containing both OS X binaries linked against Apple's >> Cocoa and friends, as well as Linux binaries linked against GNUstep. > > Manually merging the Mac OS X specific parts into the GNUstep bundle and > sprinkling some links on top might work, though I never tried that. Also you > should keep in mind that this is only ever useful if you have tight control > over all deployment environments, otherwise you're bound to end up in trouble > because of mismatched library versions, etc. > > Niels _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
