Re: linking to a different framework version
Re: linking to a different framework version
- Subject: Re: linking to a different framework version
- From: Shripada Hebbar <email@hidden>
- Date: Tue, 12 Feb 2008 10:25:57 +0530
Hi John
Best thing to do is to use the 10.5 SDK but set the deployment target as
10.4. And check dynamically for the leopard only API and make sure
they are
not called in Tiger. This would enable you to use new features in
10.5. Also
the dynamic loading of appropriate frameworks will be automatically
taken care
by loading the framework from the frameworks folder of the system
folder of the OS
its running.
Best Regards
Shripada
Hello.
I'm working in Xcode 3 and building against the 10.5 SDK. My app
embeds
Python so I must link against the Python.framework. The 10.5
Python.framework provides 2 versions of Python: 2.3 and 2.5. My app
needs
to run on a clean install of Tiger, thus I need to be able to link
against
Python 2.3 (Tiger shipped with Python 2.3.5). My Deployment target
is set to
10.4.
How exactly can I force linking against the Python 2.3 within the
system's
Python.framework?
Or perhaps more appropriate, given my constraints, how can I ensure
my app
will run/launch under Tiger (if perhaps there's another way to go
about
this)?
As well, is there a way I could work the linking such that I get the
"latest" Python depending where I run? If I force linking to the 2.3 I
assume when I run on Leopard it'll use the 2.3 Python. But if I'd
like in
this case to load the 2.5 Python... well, is there some way to get
this to
work, such that the app's runtime always picks the "latest" Python?
If not,
that's ok. The main thing is being able to build under Leopard and
10.5 SDK
but still run under Tiger, given my Python situation.
Thank you.
--
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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