Set the CPATH environment variable in your shell (e.g., put this in your .zshrc assuming you're using zsh):
export CPATH=`xcrun --show-sdk-path`/usr/include
And then try to build your project again.
The OP related to how to install the headers in /usr/include, not how to point clang to the headers wherever they may be.
MacOS System Integrity ...
Maybe things have changed since this question was originally asked but I had no trouble downloading command-line tools from here:
(I did this after deleting XCode to save about 13 GB of disk space).
I suspect this will be considered off-topic for the site, but nevertheless…
As it currently exists, Xcode is completely incompatible with iOS. Presumably at some in the future there will be some way to develop at least with Swift on iOS.
The only real answer is, of course, that no one who knows the answer to this can or will say, so there can be no real ...
Here is a tweak that you can try:
Go to Finder -> Applications
Move Xcode.app to trash. (Here it will ask you if you want to cancel update).
Agree to cancel the update.
Go to Trash -> Xcode.app, right-click and click on "Put Back"
Re-start using Xcode and continue with your work.
Also, while you wait for XCode to update and you are in a slow internet ...
You need to have Xcode 11 installed for this to work. Xcode 10.x won't recognize iOS 13.
Try logging out and in of App Store app on your Mac. If it doesn't work you try restarting your Mac. If that fails too, attempt a reinstall of Xcode from the App Store.
The Xcode 11 release notes on Apple Developer website says it requires at least macOS Mojave 10.14.4 to run. In my personal experience, I was unable to run it on macOS Mojave 10.14.4 and was asked to update to 10.14.6.
Coming to the Mac requirement, any Mac capable of running macOS Mojave 10.14.6 can run Xcode 11. Subsequent releases of Xcode will ...
Xcode 11 requires a Mac running macOS Mojave 10.14.4 or later.
The download from the Mac App Store is 7.6 GB.
with only 11 GB left on my hard drive
I would suggest having more free space before trying to download and unpack the app.
Assuming you installed gcc using brew, run brew info gcc. Find the path similar to /usr/local/Cellar/gcc/9.2.0. Go the that directory and find gcc file in bin. Copy the path name and paste it in Cmake (assuming GUI) as follows.
After cleaning cache in File -> Delete cache, start afresh in Tools -> Configure. Specify "Unix Makefiles" instead of Xcode and ...
My problem was due to iCloud.
All my projects were inside documents folder which is iCloud folder.
Because iCloud settings in my MacBook was with the optimize option, the content of files weren’t allocated locally in the hard drive but remotely in iCloud. That was the cause for unresponsiveness of Xcode when loading the project or even starting new one.
The owner of the /usr/local/include/c++ seems to be changed, which indicates you may used sudo with command brew. Never use sudo brew.
Firstly, fix the ownership recursively.
sudo chown -R "$USER":admin /usr/local/*
Secondly, relink the package gcc.
brew unlink gcc
brew link --overwrite gcc
How to fix homebrew permissions?
I don't think there is a definitive answer, because it's likely to depend on the specific Mac & how the data aligns to sector sizes when written. You'd see the same thing if you wrote a 1GB movie file & 1GB of small text files to a drive. The byte count may be the same, but the space used on disk would not.
If you look at the three basic ways to see ...
There's really no easy way to produce a definite answer for you. The definite answer varies from system to system.
You could get the definitive answer by freeing a small amount of disk space. Taking a full backup of your system. Try installing. When it fails, restore from backup. Repeat until you have the definitive answer.
It would be an unrealistic ...
The shape of the corners cannot be described as an arc. It can however be reproduced using public API since iOS 11. UIBezierPath.init(roundedRect:cornerRadius:) will create a rectangle with continuous rounded corners.
iOS 13 introduced an explicit cornerCurve ...
Xcode command line tools is a separate package for Xcode
Download Command Line Tools for Xcode from developer.apple.com/download/more and install it again.
source: Installing Xcode Command Line Tools
Useful for troubleshooting
Only install Xcode CLI tool, since most of the ports work without Xcode although there's a warning during use.
Quote from Google Summer of Code 2019 for MacPorts
Phase out dependency on Xcode (done in the main repo)
MacPorts currently requires a full Xcode installation, even though a lot of ports will install just fine with the Command Line Tools ...
You might be close, but I downloaded from the developer website and I had freed ~22 GB.
Try freeing up some more, like cache or movies you have watched, or software you don't use.
How can I figure out what's slowly eating my HD space?
Reduce size of the Xcode application
Gigabytes of disk space shown as hidden space in DaisyDisk
The Mac in question does not support a new enough macOS to install the latest versions of Xcode required to build an app that can on the App Store.
However, you could use an online build service in order to be able to develop and test apps on this Mac. For example you could use your Cordova project with Monaca - they have a free plan where you can do 2 ...
Is there any way to develop iOS apps on a MacPro 2,1 in 2019?
No. I'm afraid you've bought yourself a boat anchor. Developing iOS applications requires you to run a current version of XCode, which in turn requires a current version of macOS.
The MacPro2,1 was produced between mid-2007 and early 2008; the processor in this machine does not support some ...