Re: Cannot include Carbon on Mojave

> On May 15, 2019, at 8:07 AM, Glenn L. Austin wrote: > > Actually, the screw ups are on those software developers who write their code > based upon SDK behavior, not documentation. Yes, Apple sometimes makes > mistakes, but more often the "mistake" is that Apple fixed a bug (isn't that >

Re: Cannot include Carbon on Mojave

Actually, the screw ups are on those software developers who write their code based upon SDK behavior, not documentation. Yes, Apple sometimes makes mistakes, but more often the "mistake" is that Apple fixed a bug (isn't that what an "unintended side-effect" is?) that a software developer

Re: Cannot include Carbon on Mojave

Thanks for the feedback Aandi. I actually made it work in Mojave, at least it looks so now. I need to stick with XCode 9.4 forever and old Intel IPP as well though... It's always a nightmare with Apple... Compared to MSVC, where you buy a new machine, install MSVC and it just works, done... Oh

Re: Cannot include Carbon on Mojave

Thanks Chris! Interesting read. Btw. g++ only invokes clang, I suppose it handles some potential argument transformation. Cheers! Vojtech st 15. 5. 2019 v 1:28 odesílatel Chris Hanson napsal: > On May 14, 2019, at 8:29 AM, Vojtěch Meluzín > wrote: > > > > Here's the command line: > > > > g++

Re: Cannot include Carbon on Mojave

Mainly because of damn ProTools 10... When you combine Avid with it's incompetence and Apple with horrific compatibility attitude, things get messy... Cheers! Vojtech st 15. 5. 2019 v 0:16 odesílatel Jens Alfke napsal: > > > On May 14, 2019, at 2:40 PM, Vojtěch Meluzín > wrote: > > Hey

Re: Cannot include Carbon on Mojave

> On May 14, 2019, at 2:40 PM, Vojtěch Meluzín > wrote: > > 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. Well, I’m in the audio

Re: Cannot include Carbon on Mojave

… and now I look at your command line it has -arch i386 which is why the compiler isn’t defining __LP64__ automatically. You can see this with the rather useful define printing trick normal 64 bit g++ -dM -E - < /dev/null|grep LP64 shows that __LP64__ is defined but if you force 32 bit

Re: Cannot include Carbon on Mojave

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 napsal:

Re: Cannot include Carbon on Mojave

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 #endif so the include is guarded by __LP64__ which

Re: Cannot include Carbon on Mojave

On May 14, 2019, at 2:11 PM, Vojtěch Meluzín 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. Interesting. $ find /Applications/Xcode.app -name CarbonSound.h -print returns no results. Where are you

Re: Cannot include Carbon on Mojave

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.

Re: Cannot include Carbon on Mojave

> On May 14, 2019, at 12:02 PM, Vojtěch Meluzín > 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

Re: Cannot include Carbon on Mojave

I had a lot strange build errors like this when I updated to Mojave. Somehow they whet away after trying a lot for some time. Georg > Am 14.05.2019 um 20:02 schrieb Vojtěch Meluzín : > > Not really, I searched and it is still there, the headers are inside > CarbonSound framework, which is

Re: Cannot include Carbon on Mojave

Not really, I searched and it is still there, the headers are inside CarbonSound framework, which is inside Carbon framework. And as i wrote, XCode compiles fine, like there's something new... I'll need to anazy XCode's command lines apparently... Cheers! Vojtech Dne út 14. 5. 2019 18:01

Re: Cannot include Carbon on Mojave

> On May 14, 2019, at 9:29 AM, Vojtěch Meluzín > wrote: > > Hey folks, > > I have a brand new computer (as well as old one), newest XCode, Mojave > (unfortunately!). Compiling carbon.h ends up with this: > >

Cannot include Carbon on Mojave

Hey folks, I have a brand new computer (as well as old one), newest XCode, Mojave (unfortunately!). Compiling carbon.h ends up with this: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/