Re: Cannot include Carbon on Mojave
Re: Cannot include Carbon on Mojave
- Subject: Re: Cannot include Carbon on Mojave
- From: Vojtěch Meluzín <email@hidden>
- Date: Tue, 14 May 2019 23:40:00 +0200
Hey folks, that's to you all. It's all the missing 32-bit support now...
Need to revert to XCode 9, forever... The audio community just needs and
will need 32-bit support, no matter what Apple thinks.
Cheers!
Vojtech
www.meldaproduction.com
út 14. 5. 2019 v 23:24 odesílatel Roland King <email@hidden> napsal:
> CarbonSound has most definitely been removed from the current SDK, you can
> use find or grep or the really useful utility ‘ack’ to prove that
>
> If you look at the header file for carbon you’ll find
>
> #if !__LP64__
> #ifndef __CARBONSOUND__
> #include <CarbonSound/CarbonSound.h>
> #endif
>
> so the include is guarded by __LP64__ which is the define which says
> you’re building a 64 bit target. Xcode and any Xcode type build sets that
> define for you, so if you’re using g++ and your own command line, you need
> to set it somewhere, either on the command line or at the very start of any
> code to ensure it’s set everywhere.
>
> If you aren’t building for a 64 bit target, can’t really help you, do
> non-64 bit targets even exist any more and work? It’s been so long since
> Apple did the transition.
>
> On 15 May 2019, at 05:11, Vojtěch Meluzín <email@hidden>
> wrote:
>
> I know it has been deprecated, no argues there, but my point is that the
> headers are there, yet the compiler doesn't find them.
> I'm trying to find out what XCode does exactly - is there a way to display
> the actual command line XCode uses to compile the source codes?
>
> Cheers!
> Vojtech
>
>
> út 14. 5. 2019 v 22:13 odesílatel Richard Charles <email@hidden>
> napsal:
>
> On May 14, 2019, at 12:02 PM, Vojtěch Meluzín <email@hidden>
>
> wrote:
>
>
> Not really,
>
>
> Yes really, CarbonSound was depreciated in OS X v10.5. Depreciated does
> not mean that the framework has been removed from current installations of
> the OS (although that is possible). It means that developers are
> discouraged from using the API and that at some point in the future it may
> be unsupported or removed.
>
> "Apple did not create a 64-bit version of Carbon while updating their
> other frameworks in the 2007 time-frame, and eventually deprecated the
> entire API in OS X 10.8 Mountain Lion, which was released on July 24,
> 2012."
>
> https://en.wikipedia.org/wiki/Carbon_(API)
>
>
> On May 14, 2019, at 9:29 AM, Vojtěch Meluzín <email@hidden>
>
> wrote:
>
>
> Compiling carbon.h ends up with this:
>
>
>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/
>
> Carbon.framework/Headers/Carbon.h:34:10: fatal error:
> 'CarbonSound/CarbonSound.h' file not found
>
>
> My guess is that this is deliberate and Xcode is trying to warn you move
> to another API. But maybe not and you will find a workaround.
>
> --Richard Charles
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> 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:
>
> This email sent to email@hidden
>
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden