All of a sudden there’s a mysterious “.datc5c7.a42” directory at the root of my 
project (i.e. next to my Xcode project.) It appears to contain Xcode build 
data. It’s invisible in the Finder, but it shows up in git commands, which is 
annoying. Weirdly, it only seems to contain files related to one of the nested 
Xcode projects (PocketSocket) within my main project.

It seems to have been created at 10:22 this morning, though I haven’t installed 
any new version of Xcode since 7b2 last week.

Anyone else seen this?

—Jens

.datc5c7.a42
├── .datc5c7.a41
│   ├── .datc5c7.a40
│   │   ├── .datc5c7.a3f
│   │   │   ├── PocketSocket.build
│   │   │   │   ├── Debug
│   │   │   │   │   └── PocketSocket-Mac.build
│   │   │   │   │       ├── Objects-normal
│   │   │   │   │       │   └── x86_64
│   │   │   │   │       │       └── PocketSocket-Mac.LinkFileList
│   │   │   │   │       ├── 
PocketSocket-Mac-all-non-framework-target-headers.hmap
│   │   │   │   │       ├── PocketSocket-Mac-all-target-headers.hmap
│   │   │   │   │       ├── PocketSocket-Mac-generated-files.hmap
│   │   │   │   │       ├── PocketSocket-Mac-own-target-headers.hmap
│   │   │   │   │       ├── PocketSocket-Mac-project-headers.hmap
│   │   │   │   │       └── PocketSocket-Mac.hmap
│   │   │   │   └── all-product-headers.yaml
│   │   │   └── PrecompiledHeaders
│   │   │       └── PocketSocket-Prefix-fyyjxxugkjqdcjgifhhwnxycfjcn
│   │   │           └── PocketSocket-Prefix.pch.pch.hash-criteria
│   │   └── Products
│   └── Index
│       └── PrecompiledHeaders
│           └── PocketSocket-Prefix-gdzjzdlqtpepqddqwtbuewgwharr_ast
│               └── PocketSocket-Prefix.pch.pch.hash-criteria
└── ModuleCache
    └── Session.modulevalidation


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to