In my work MacBook on Monterey 12.1, /private is read only, but /tmp still is
writeable. I just create a folder there as a test.
That aside, if there’s anything I’ve learned in the week or two since I’ve been
using Xcode, it’s “don’t do what it doesn’t expect you to do”. That includes
to usin
>
> In Monterey, /tmp is now only writeable by root.
It is?
I have been storing temp files in /tmp all my life (output from all kinds of
programs), and did not notice a change when upgrading to Monterey.
/Users/zach% cd /tmp
/private/tmp% ls -ld .
drwxrwxrwt 17 root wheel 544 Feb 14 12:00 ./
On Feb 13, 2022, at 4:39 PM, Jack Brindle via Cocoa-dev
wrote:
>
> In Monterey, /tmp is now only writeable by root.
??? Does terminal.app have special privs?
~% ls -l /tmp
lrwxr-xr-x@ 1 root wheel 11 Feb 6 13:22 /tmp@ -> private/tmp
~% ls -ld /private/tmp
drwxrwxrwt 23 root wheel 736 Feb
> On Feb 13, 2022, at 4:09 PM, Gabriel Zachmann wrote:
>
> The Derived Data directory is set to /tmp (i have had that setting for years).
Oh, don’t do that.
Glad you’ve got it fixed.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please d
In Monterey, /tmp is now only writeable by root. It is quite possible that
Xcode couldn’t write there for the indexing.
When you changed to a new account, it probably changed where the derived data
went.
It used to be that /tmp was writeable by anyone. That change bit me recently as
well. Secu
> This seems to indicate an error somewhere in the Xcode prefs.
Oh, wow, maybe I have resolved the issue!
The Derived Data directory is set to /tmp (i have had that setting for years).
Now, in Xcode / Preferences / Locations / Derived Data / Advanced,
I set Custom = Relative to Derived Data.
(Be
This seems to indicate an error somewhere in the Xcode prefs.
Try using it in that new user is aways am option.
Or copy the project back into another folder and see if the original user can
open the project from the other folder.
Just the two guesses I have at the moment.
Cheers,
Alex Zavatone
On 13 Feb 2022, at 1:07 pm, Gabriel Zachmann via Cocoa-dev
wrote:
> Just now, I have tried a few other things.
> I deleted some folders in ~/Library/Deverlopers (caches, log files, devices).
> Interestingly, there is no ~/Library/Deverloper/Xcode/DerivedData! (which
> should contain the indexin
>
> Sort of straw-grasping I would try with Xcode under these circumstances?
>
> Try changing the target CPU/OS setting to something else, build, and see if
> the indexing works.
>
> If it does, make the minimal changes needed to appropriately build your
> target.
>
Thanks a lot for the straw ,
This is, indeed, strange.
I tried it, as you suggested, with a new user account on the very same machine.
Everything works just fine in a copy of the project under that pristine account.
Even when I launch the .xcodeproject in my real home, the indexing works.
It just does not work in my home.
J
Sort of straw-grasping I would try with Xcode under these circumstances…
Try changing the target CPU/OS setting to something else, build, and see if the
indexing works.
If it does, make the minimal changes needed to appropriately build your target.
If it doesn’t, discard straw.
Kirk Kerekes
Here’s an idea. Create a new user on your Mac. Open the project from that new
user and see if it indexes.
It worked fine on my Mac
Good luck.
> On Feb 12, 2022, at 8:24 AM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> Here is another attempt at getting to the root of the indexer problem I a
Here is another attempt at getting to the root of the indexer problem I am
experiencing.
First of all, thanks a lot for your helpful hints, albeit they did not resolve
the issue.
Here is - for recap - the description in a nutshell of my original post:
A few weeks ago, indexing in Xco
> I have come across issues where a code syntax error messes up indexing—are
> you able to do a full, successful compilation?
Yes, I think so.
Have done Product / Clean Build Folder ,
then quit Xcode, then launched again.
The project builds fine, no warnings.
But I still have a hunch it's in th
I have come across issues where a code syntax error messes up indexing—are you
able to do a full, successful compilation? Other than that, I have heard that
some issues might require a system restart, i.e. 1) quitting Xcode; 2) deleting
derived data (if you use a shared location you might also w
Thanks a lot for your response.
I had tried that already, to no avail.
I am seeing lots of "Crash detected during compilation"
in Xcode's indexing log.
Best regards, Gabriel
> On 6. Feb 2022, at 19:18, Rob Petrovec wrote:
>
> Quit Xcode, delete the DerivedData directory for your project an
Over several weeks, I’ve had the most annoying problem with Xcode and pods with
the sandbox always being out of sync.
Guess what fixed it? Quitting and restarting Xcode. Sometimes this product
just reminds you of Windows 3.1.
Best of luck.
Gabriel want me to try your project out in Xcode 1
Quit Xcode, delete the DerivedData directory for your project and re-open your
project. That should trigger a re-index and a full rebuild of your product.
The default location for the DerivedData directory is in
~/Library/Developer/Xcode/DerivedData/-. You can also configure it to be in your s
18 matches
Mail list logo
