Re: xCode troubles

[John McCall]

On 15 May 2019, at 0:35, Richard Charles wrote:


On May 14, 2019, at 10:19 PM, John McCall  wrote:

It's unfixed because it's apparently very hard to reliably reproduce. 
 If you have reliable steps for reproduction, we'd be very 
interested.


Perhaps Peter Hudson could send you his corrupted project before it 
was reset. That might be useful.


If Peter is willing to share that project (under Apple's usual promises 
of confidentiality, if it can't be reduced), together with instructions 
for how to reproduce the problem, that would be great.


John.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Richard Charles]

> On May 14, 2019, at 10:19 PM, John McCall  wrote:
> 
> It's unfixed because it's apparently very hard to reliably reproduce.  If you 
> have reliable steps for reproduction, we'd be very interested.

Perhaps Peter Hudson could send you his corrupted project before it was reset. 
That might be useful.

--Richard Charles

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[John McCall]

On 15 May 2019, at 0:03, Ben Kennedy wrote:

The phenomenon you're describing is a long-standing bug in Xcode that 
Apple does not seem interested in fixing.


I finally filed it last November as rdar://46203599. It was closed as 
a duplicate of rdar://9706748 (!). (That's actually rather alarming, 
because it's 36.5 million numbers earlier; judging my library of old 
and still-open bugs, that would put it at mid-2011 or so...)


It's unfixed because it's apparently very hard to reliably reproduce.  
If you have reliable steps for reproduction, we'd be very interested.


John.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Ben Kennedy]

The phenomenon you're describing is a long-standing bug in Xcode that Apple 
does not seem interested in fixing.

I finally filed it last November as rdar://46203599. It was closed as a 
duplicate of rdar://9706748 (!). (That's actually rather alarming, because it's 
36.5 million numbers earlier; judging my library of old and still-open bugs, 
that would put it at mid-2011 or so...)

-ben


> On 14 May 2019, at 3:20 pm, Peter Hudson  wrote:
> 
> Hi Jens
> 
> Sorry my description was not clear. What happened is that the edit widget 
> panel would appear on the right hand side - but would have no tools in it. 
> When I selected an object in the storyboard ( e.g. a table view) none of the 
> appropriate editing tools would appear in any of the panels on the right. 
> Hence any editing of GUI was impossible. 
> 
> Richard Charles’s response earlier in the day has however fixed it. He 
> suggested removing a couple of files in the project bundle. 
> 
> Many thanks
> 
> Peter 
> 
> 
> 
> 
>> On 14 May 2019, at 23:05, Jens Alfke  wrote:
>> 
>> 
>> 
>>> On May 14, 2019, at 3:39 AM, Peter Hudson  wrote:
>>> 
>>> xCode has just decided ( for the 20th time this week ) that I don’t deserve 
>>> any UI tools in Interface Builder - as in the panel on the right hand side 
>>> of the main window.  I have tried everything I can think of to try to get 
>>> them back - like restarting xCode, opening different files etc.
>> 
>> You mean that clicking the Show Inspectors button on the right end of the 
>> toolbar didn’t work, nor did Cmd-Opt-zero?
>> 
>> —Jens
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/ben%40zygoat.ca
> 
> This email sent to b...@zygoat.ca

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Peter Hudson]

Hi Jens

Sorry my description was not clear. What happened is that the edit widget panel 
would appear on the right hand side - but would have no tools in it. When I 
selected an object in the storyboard ( e.g. a table view) none of the 
appropriate editing tools would appear in any of the panels on the right. Hence 
any editing of GUI was impossible. 

Richard Charles’s response earlier in the day has however fixed it. He 
suggested removing a couple of files in the project bundle. 

Many thanks

Peter 




> On 14 May 2019, at 23:05, Jens Alfke  wrote:
> 
> 
> 
>> On May 14, 2019, at 3:39 AM, Peter Hudson  wrote:
>> 
>> xCode has just decided ( for the 20th time this week ) that I don’t deserve 
>> any UI tools in Interface Builder - as in the panel on the right hand side 
>> of the main window.  I have tried everything I can think of to try to get 
>> them back - like restarting xCode, opening different files etc.
> 
> You mean that clicking the Show Inspectors button on the right end of the 
> toolbar didn’t work, nor did Cmd-Opt-zero?
> 
> —Jens
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Vojtěch Meluzín]

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 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 community*, and I don’t need 32-bit support. Why is
> it necessary, except for supporting very old computers (Apple hasn’t
> shipped a 32-bit CPU since 2006**) or supporting badly-written source code
> that doesn’t work in 64-bit?
>
> —Jens
>
> * I own Ableton, Logic, a bunch of hardware synths, and a rack of Eurorack
> modules.
> ** According to
> https://apple.stackexchange.com/questions/99640/how-old-are-macs-that-cannot-run-64-bit-applications
>  ,
> a thread from 2015 that states "you can very confidently forget about 32bit
> if you're developing an application”.
>
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Jens Alfke]

> 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 community*, and I don’t need 32-bit support. Why is it 
necessary, except for supporting very old computers (Apple hasn’t shipped a 
32-bit CPU since 2006**) or supporting badly-written source code that doesn’t 
work in 64-bit?

—Jens

* I own Ableton, Logic, a bunch of hardware synths, and a rack of Eurorack 
modules.
** According to 
https://apple.stackexchange.com/questions/99640/how-old-are-macs-that-cannot-run-64-bit-applications
 

 , a thread from 2015 that states "you can very confidently forget about 32bit 
if you're developing an application”.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Jens Alfke]

> On May 14, 2019, at 3:39 AM, Peter Hudson  wrote:
> 
> xCode has just decided ( for the 20th time this week ) that I don’t deserve 
> any UI tools in Interface Builder - as in the panel on the right hand side of 
> the main window.  I have tried everything I can think of to try to get them 
> back - like restarting xCode, opening different files etc.

You mean that clicking the Show Inspectors button on the right end of the 
toolbar didn’t work, nor did Cmd-Opt-zero?

—Jens
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Roland King]

… 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 architecture

g++ -arch i386 -dM -E - < /dev/null|grep LP64

it isn’t defined. 

So the basic ‘reason’ you’re getting a failure is because CarbonSound is (and 
may for some time have been) only included in 32bit builds. Apple has now 
removed the actual package from the SDK but left the include in there. This was 
probably not noticed as everyone is building 64 bit so the macro is defined so 
the header include was skipped and it didn’t matter that it’s not there. So you 
could say the header is broken, it kind of is, they should have just removed it 
entirely when they removed the package. 



> On 15 May 2019, at 05:23, Roland King  wrote:
> 
> 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 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  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 
>> napsal:
>> 
 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
>>> 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 
>>> 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 (Cocoa-dev@lists.apple.com)
>> 
>> 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:
>> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
>> 
>> This email sent to r...@rols.org
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
> 
> This email sent to r...@rols.org

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Vojtěch Meluzín]

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:

> 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 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 
> 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 
> napsal:
>
> 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
> 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 
>
> 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 (Cocoa-dev@lists.apple.com)
>
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
>
> This email sent to r...@rols.org
>
>
>
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cocoa-dev Digest, Vol 16, Issue 40

[Vojtěch Meluzín]

You may be right, apparently this needs to be installed using some package,
at least according to google. Anyways I just found the potential cause -
XCode 10 doesn't support 32-bit apps anymore! So that may be it, since this
stuff is 64-bit only, they probably left the traces there... Oh well,
hopefully XCode 9.4 will be fine. Since I'll probably need to support
32-bit apps for many years, I'm stuck with that... and so is the entire
audio community... Apple...

Cheers!
Vojtech

út 14. 5. 2019 v 21:42 odesílatel Steven Woolgar 
napsal:

>
> 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
>
>
> I just checked on my machine. There is no CarbonSound.h file in the:
>
>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Carbon.framework/Frameworks/CarbonSound.framework/Headers/
>
> Path.
>
> There is a CarbonSound.r file, but no .h file.
>
> Also, your error is:
>
>
> /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
>
> Carbon.framework/Headers/* does not contain that file either. Seems like
> you have a path issue, above and beyond the fact that the file no longer
> exists in the Carbon umbrella framework.
>
>
>
> W.
>
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Roland King]

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 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  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 
> napsal:
> 
>>> 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
>> 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 
>> 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 (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
> 
> This email sent to r...@rols.org

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Marco S Hyman]

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 finding it?  I see that the file is 
reference in some other headers, but the file itself seems not to exist.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Vojtěch Meluzín]

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

> > 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
> 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 
> 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 (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Richard Charles]

> 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 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  
> 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 (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Georg Seifert]

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 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 uživatel Richard Charles 
> napsal:
> 
>> 
>>> 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:
>>> 
>>> 
>> /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
>> 
>> CarbonSound was depreciated in OS X v10.5.
>> 
>> 
>> https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/OSX_Technology_Overview/SystemFrameworks/SystemFrameworks.html
>> 
>> It looks to me like Apple is making good on their promise.
>> 
>> --Richard Charles
>> 
>> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/georg.seifert%40gmx.de
> 
> This email sent to georg.seif...@gmx.de

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Vojtěch Meluzín]

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 uživatel Richard Charles 
napsal:

>
> > 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:
> >
> >
> /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
>
> CarbonSound was depreciated in OS X v10.5.
>
>
> https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/OSX_Technology_Overview/SystemFrameworks/SystemFrameworks.html
>
> It looks to me like Apple is making good on their promise.
>
> --Richard Charles
>
>
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Cannot include Carbon on Mojave

[Richard Charles]

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

CarbonSound was depreciated in OS X v10.5.

https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/OSX_Technology_Overview/SystemFrameworks/SystemFrameworks.html

It looks to me like Apple is making good on their promise.

--Richard Charles

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Cannot include Carbon on Mojave

[Vojtěch Meluzín]

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/
Carbon.framework/Headers/Carbon.h:34:10: fatal error:
'CarbonSound/CarbonSound.h' file not found

Here's the command line:

g++ -x c++ -g -fexceptions -std=c++17 -stdlib=libc++ -arch i386
-fexceptions -mfix-and-continue -gdwarf-2 -fvisibility=hidden
-fpascal-strings -fasm-blocks -c mlibrary/mlibrary.cpp -o !temp/mlibrary.o

Until now it worked just fine on every OSX version so far. The weird part
is that creating an empty project in XCode lets me include
, so it seems Apple messed the toolset somehow. Any ideas?

Thanks for any help!
Vojtech
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Peter Hudson]

Thanks Richard !
Removing those two files has worked - I have my GUI tools back !
Peter

> On 14 May 2019, at 15:54, Richard Charles  wrote:
> 
> 
>> On May 14, 2019, at 4:39 AM, Peter Hudson  wrote:
>> 
>> Hi All
>> 
>> xCode has just decided ( for the 20th time this week ) that I don’t deserve 
>> any UI tools in Interface Builder - as in the panel on the right hand side 
>> of the main window.  I have tried everything I can think of to try to get 
>> them back - like restarting xCode, opening different files etc.
> 
> When a single file is opened the default is no toolbar, no left side 
> navigator, and no right side utilities.
> 
> When a project is opened then you should get everything. Does this happen 
> when you open a brand new project?
> 
> You can reset an existing project by opening the xcodeproj bundle and 
> discarding the xcworkspace bundle and xcuserdata folder. Keep the pbxproj 
> bundle.
> 
> --Richard Charles
> 

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Richard Charles]

> On May 14, 2019, at 4:39 AM, Peter Hudson  wrote:
> 
> Hi All
> 
> xCode has just decided ( for the 20th time this week ) that I don’t deserve 
> any UI tools in Interface Builder - as in the panel on the right hand side of 
> the main window.  I have tried everything I can think of to try to get them 
> back - like restarting xCode, opening different files etc.

When a single file is opened the default is no toolbar, no left side navigator, 
and no right side utilities.

When a project is opened then you should get everything. Does this happen when 
you open a brand new project?

You can reset an existing project by opening the xcodeproj bundle and 
discarding the xcworkspace bundle and xcuserdata folder. Keep the pbxproj 
bundle.

--Richard Charles

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Peter Hudson]

Not sure how I would trash xCode preferences. 
Peter

> On 14 May 2019, at 11:48, Sandor Szatmari  
> wrote:
> 
> Peter,
> 
>> On May 14, 2019, at 06:39, Peter Hudson  wrote:
>> 
>> Hi All
>> 
>> xCode has just decided ( for the 20th time this week ) that I don’t deserve 
>> any UI tools in Interface Builder - as in the panel on the right hand side 
>> of the main window.  I have tried everything I can think of to try to get 
>> them back - like restarting xCode, opening different files etc.
> 
> Did you try trashing Xcodes preferences?
> 
> Sandor
>> But alas, no GUI tools for me !
>> 
>> Any ideas on how to fix this would be most welcome.
>> 
>> MacOS 10.14.3 / xCode 10.2 / swift project for macOS
>> 
>> 
>> Peter
>> ___
>> 
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>> 
>> 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:
>> https://lists.apple.com/mailman/options/cocoa-dev/admin.szatmari.net%40gmail.com
>> 
>> This email sent to admin.szatmari@gmail.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Totte Alm]

Hi,

yes, has been a pain the past weeks, needs to quit XCode 10 times a day (unless 
it doesn’t crash first)

/ Totte


> 14 maj 2019 kl. 12:39 skrev Peter Hudson :
> 
> Hi All
> 
> xCode has just decided ( for the 20th time this week ) that I don’t deserve 
> any UI tools in Interface Builder - as in the panel on the right hand side of 
> the main window.  I have tried everything I can think of to try to get them 
> back - like restarting xCode, opening different files etc.
> But alas, no GUI tools for me !
> 
> Any ideas on how to fix this would be most welcome.
> 
> MacOS 10.14.3 / xCode 10.2 / swift project for macOS
> 
> 
> Peter
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/totte%40code66.se
> 
> This email sent to to...@code66.se

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: xCode troubles

[Sandor Szatmari]

Peter,

> On May 14, 2019, at 06:39, Peter Hudson  wrote:
> 
> Hi All
> 
> xCode has just decided ( for the 20th time this week ) that I don’t deserve 
> any UI tools in Interface Builder - as in the panel on the right hand side of 
> the main window.  I have tried everything I can think of to try to get them 
> back - like restarting xCode, opening different files etc.

Did you try trashing Xcodes preferences?

Sandor
> But alas, no GUI tools for me !
> 
> Any ideas on how to fix this would be most welcome.
> 
> MacOS 10.14.3 / xCode 10.2 / swift project for macOS
> 
> 
> Peter
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/admin.szatmari.net%40gmail.com
> 
> This email sent to admin.szatmari@gmail.com
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

xCode troubles

[Peter Hudson]

Hi All

xCode has just decided ( for the 20th time this week ) that I don’t deserve any 
UI tools in Interface Builder - as in the panel on the right hand side of the 
main window.  I have tried everything I can think of to try to get them back - 
like restarting xCode, opening different files etc.
But alas, no GUI tools for me !

Any ideas on how to fix this would be most welcome.

MacOS 10.14.3 / xCode 10.2 / swift project for macOS


Peter
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com