Have you read TN2064: Ensuring Backwards Binary Compatibility - Weak Linking
and Availability Macros on Mac OS X
http://developer.apple.com/technotes/tn2002/tn2064.html
Larry
On 11/14/04 3:53 PM, Ando Sonenblick didst favor us with:
> That's a pretty smart idea.
>
> Know where I can get the jaguar CFM CarbonLib?
>
> I don't have any apple CarbonLib on my Jaguar install?!
>
>> I'd link against the jaguar version of CarbonLib and use CFBundle to
>> obtain HIWindowChangeFeatures when it exists.
>>
>> Fred
>
>
>>
>> On 14 Nov 2004, at 19:53, Ando Sonenblick wrote:
>>
>>> Gang,
>>>
>>> I make this call in my CFM app (that staticly includes the CarbonLib
>>> in System/Library/CFMSupport):
>>>
>>> HIWindowChangeFeatures(window, 0, kWindowIsOpaque);
>>>
>>> This is fine on Panther, but trying to run my app on jaguar results
>>> in the system saying the app cannot run because of a shared library
>>> error and then indicates HIWindowChangeFeatures as the culprit.
>>>
>>> Since I really don't want to have two binaries, one for jaguar and
>>> one for panther, is there a way for me to dynamically get the address
>>> of HIChangeWindowFeatures and if it is available call it, and if not
>>> skip calling it?
>>>
>>> Can I do something like
>>> LoadFrameworkBundle/CFBundleGetFunctionPointerForName on CarbonLib?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
