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.
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
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 - a
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 Interfa
> 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 ge
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
>
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.
> 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/M
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
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 insi
> 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 discoura
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. 201
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
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
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,
hope
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:
… 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 archi
> 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
> b
> 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 comm
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,
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 o
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; j
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 alarm
> 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 u
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
25 matches
Mail list logo
