Migrating from MPW CFM to XCODE Mach-O
Migrating from MPW CFM to XCODE Mach-O
- Subject: Migrating from MPW CFM to XCODE Mach-O
- From: Paul Chadha <email@hidden>
- Date: Fri, 10 Jun 2005 12:03:50 +0900
Hi Folks -
We're now in the process of migrating our entire Carbon Mac OS X code from
MPW-CFM (it works!) to XCODE v2.1.
We've started work with about 50% of our core code and so far things look
pretty good in terms of compliation (but its good enough for us to start
debugging/testing).
I'm providing some background and details first so that my questions will
make more sense.
Our entire code base is nothing but a set of Shared Libraries, Static
Libraries and CFM plug-ins(code in data fork; resources in resource fork).
We use the CFM fcns for loading the Shared Libs manually and binding to it.
Same goes for the plug-ins.
What we used to do in generating the SharedLib/Plug-ins was to export a
single point of entry as its main interface (to simplify binding) and bind
through these single entry points.
Our plug-ins are detected dynamically (via File type/Creator Code) when our
application(s) are launched. So we don't hard bind/link against them (ie.
we can have any number of plug-ins it doesn't matter). We don't even hard
bind against our Shared Libs.
Having gone through the Runtime Arch docs for Mach-O and the new mechanism
of organizing executables For OS X, it seems as though that the way to go
for our plug-ins is to use Bundles and the Shared Libs/Static Libs are
pretty much as they are.
We have the following questions and would appreciate your response.
#1. Creating a C++ Shared Mach-O shared library/Bundle
Can we export a single "C++" main entry interface from the Shared Lib/Bundle
we generate? If so, what is the XCODE option to use? If not what do we do?
For a Bundle, how do we bind to the main entry point - are there equivalents
of MakeDataExecutable/GetMemFragment?
#2. Resource Fork based resource for Bundles
If we switch to generating Carbon BUNDLES for our plug-ins, can we still
have the resources in the resource fork without having to go through the
Data Fork based resources? Does such an option exist? If so - how can we
accomplish it using the tools from XCODE? Is there a REZ tool as such?
We understand the point of a Bundle is to seperate your Code/Resource/other
files - but if we can avoid it, we'd like to for our first migration stage -
so that once we get everything up and running then we can move to BUNDLES.
#4. Debugging
Will the XCODE debugger in general be able to handle debugging through the
Shared Libs/Plug-ins (we've been using gdb so far - but would rather use the
XCODE debugger if possible)?
Thanks & Regards -
Paul Chadha
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden