> On Sep 30, 2014, at 12:49, Motti Shneor <su...@bezeqint.net> wrote: > > Hello everyone. This seems to be an upside-down question, but bare with me... > > Our Mac Client-side application can (sadly) only be built and run in > 32bit-only. Reason is: bit parts of it are legacy 32bit-only C++ code shared > with other platforms (Windows, Android, Linux, etc.) client code as well as > the Windows-only server. This code contains networking-protocol code which > is 64bit unsafe, and so it can't really be replaced. > > Until All platforms and products move together to 64bit, we're bound to build > our app 32bit only. > > Now I'm building a new module for this application as an external private > dynamic framework. I would like to use ARC, and the new niceties of modern > Obj-C runtime for the new framework, but these are only available in > 64bit-only builds. > > So… Could my 32bit-only Mac Application depend-on, load, link, and use, a > 64bit-only framework?
No. You basically have two options: 1) Build a helper app or tool that is 64-bit (and can therefore link 64-bit code) and call that too, from your 32-bit app 2) Move your 64-bit-unsafe code into a helper tool and make the rest of the app 64-bit. Both options rely on having two separate processes, one running 32-bit code and one running 64-bit code, and only differ in which you put in the main app and which you put in the helper. -- Clark Smith Cox III clarkc...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
