Date
1 - 3 of 3
Xcode: Installing components
|
Gerriet M. Denkmann
After migrating to macOS 13.1 when I first started Xcode (9.1) it told me that it had to install some components.
What are these “components” and where do they live? Also: My macOS 13 partition does not have /usr/include anymore. Where are the include files to be found? (Xcode has no problems, it seems to know where to look for include files). “find” (after ignoring several folders where ordinary people have no right to look) finds: V = Volume where Xcode lives (not the boot volume for macOS 13.1) /V/Applications/Xcode.app/Contents/Developer/Platforms/[some platform].platform/Developer/SDKs/[some platform].sdk/usr/include /V/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include /V/usr/include Should these include folders all be identical? Gerriet. |
|
|
|
Quincey Morris
On Nov 20, 2017, at 22:17 , Gerriet M. Denkmann <g@...> wrote:
I think it’s installing components that allow access to devices. I have no idea what’s modified.
No. [1] contains a complete Unix C build environment (tools, headers, libraries) that’s used when you build command line tools or otherwise make use of the Unix execution environment from within Xcode. There are different ones depending on the platform/SDK, but they are encapsulated within Xcode so that they don’t get mixed up with tools etc that are built outside the Xcode environment, since /usr can be highly customized under other build systems. [2] is (I think) the same kind of thing, but left over from an earlier Xcode strategy where there was a separate Xcode build environment, but only one. This didn’t work so well if different versions of Xcode were installed simultaneously. (Remember when that was a thing?) I don’t have those files, because (I think) my Mac isn’t old enough. [3] is a standard location for user-provided or user-customized build tools, so it may contain things you’ve downloaded or modified. The general idea is that anything you do from or within Xcode is a standardized execution environment that you can’t mess up by other Unix-compatible development activities. /usr is yours to mess up without having to worry it will cause Xcode to fall in a crashing heap. |
|
|
Shared libraries for talking to iOS devices. Possibly debugger & profiler infrastructure (stuff for getting access to other processes.) Etc. Xcode has been installing this stuff since at least version 6, IIRC. Also: My macOS 13 partition does not have /usr/include anymore. I haven’t seen a /usr/include directory on Mac OS in years, ever since Xcode switched to using internal SDKs for building. —Jens |
|
|