Install Xcode On Catalina

 

Now go back to Xcode 11 and into preferences components and install the 12.2 simulator. Note you can’t do this in Xcode 10 on Catalina due to system read-only partitions. Once you’ve done all you should have simulators setup for 12.2, 12.4 and 13.1. Using the CLI you can now build an app for iOS 13 SDK (with 7.5.x or 8.2.x) using. In this video we'll setup environment to work with SwiftUI in order to run SwiftUI apps on iOS and macOS. SwiftUI requires XCode 11 and macOS Catalina to pro. Open your terminal to begin the process of installing command-line tools on macOS Catalina. With your terminal opened, type the command below into the prompt and press the return key to execute it. After executing the command below a pop-up window should open with the option to install. The popped-up window should look similar to the image below. 5) Install Xdebug. If the command: $ pecl install xdebug Fails due to the phpize not returning the correct information, or it's trying to write to folders it cannot, or it cannot find php.h, etc, as it did for me and what started this post, try the following: First, you need to make sure that Xcode and the command line tools installed. Installing Homebrew. First, we need to install Homebrew. Homebrew allows us to install and compile software packages easily from source. Homebrew comes with a very simple install script. When it asks you to install XCode CommandLine Tools, say yes. Open Terminal and run the following command.

Mac users with macOS Mojave and macOS Catalina, and new operating systems in place can now install Command Line Tools from the Xcode IDE without needing to install the entire Xcode package, or opening an Apple developers account.

Did you know: Using Xcode app leaves behind a lot of junk files a.k.a. 'development junk.' These files are usually hidden from view but you can delete them with a Mac maintenance app CleanMyMac X.

In this article, we cover how you can install this optional and highly useful Command Line Tools package.

X code 11. Credit: developerinsider

What is the Xcode Command Line Tools package?

For Mac power users — we wouldn't recommend downloading this unless you are comfortable with Terminal — the Xcode Command Line Tools package gives you a complete Unix toolkit accessible through Terminal. No developer account needed and you don't need to download the entire — and quite large Xcode package of executables.

Within the Xcode Command Line toolkit, Mac users gain access to numerous useful tools, utilities, and compilers, including make, GCC, clang, perl, svn, git, size, strip, strings, libtool, cpp, and many others. All of these commands are a default part of Linux systems and programs.

We recommend following these steps for those with the following operating systems running on a Mac: macOS 10.13 High Sierra, macOS 10.14 Mojave, and macOS 10.15 Catalia onward. It isn't always possible to download these Xcode Command Line Tools, following these steps, on Mac’s running older operating systems. Other ways to install command tools and gcc (without needing Xcode) is available through the Apple Developer website.

Install Xcode On Catalina

Here is how you install Xcode Command Line Tools.

How to install Xcode Command Line Tools?

  1. Go to Terminal in /Applications/Utilities/.
  2. Input the following command string in Terminal: xcode-select —install
  3. In the same way when you are downloading new software and apps, a popup update window will appear asking you: “The xcode-select command requires the command line developer tools. Would you like to install the tools now?”
  4. Select confirm by clicking Install.
  5. Wait for the Xcode Command Line Tools package to install. It is around 130 MB and usually installs fairly quickly; although it depends on your connection.
  6. Once everything is installed, the installer goes away and you should be able to any of the new commands that you’ve now got access to. Enjoy using your new Unix command line tools!

Alternative way to install command line tools
If the Terminal combination didn't work, open the Finder > Go to Folder...menu.
Paste in the following path:/System/Library/CoreServices

Install Xcode On Catalina

In that location, find the app called Install Command Line Developer Tools.app — it will have a blue globe icon.
Click this app and then try the Terminal method explained above.

With this new download, you should have access to 61 Unix command line tools. For example, one of the advantages of having these tools is you can install new apps and software directly from the source code instead of needing to go through the package manager and usual download route.

Install Xcode 12 On Catalina

To access or view everything you've now got, go to the following directory:

/Library/Developer/CommandLineTools/

Please note, this is the root /Library of your macOS/OS X, not the ~/Library directory.

All of these tools can also be found in: /Library/Developer/CommandLineTools/usr/bin/

These tools like small executable apps (which they are):

What happens if I encounter problems downloading these?

If you get an error message that says “Can’t install the software because it is not currently available from the Software Update server”, it means you've already got the Xcode package on your Mac. Mac OS X 10.9 onward, Xcode was already installed, which is why you aren't able to download these tools. However, what you can do is uninstall the entire Xcode app if you'd prefer to only access these tools and not a whole load of software that isn’t going to be of much use.

Watch out for Xcode junk

Install Xcode 10.3 On Catalina

The Xcode junk is one of those types of clutter that is keeps accumulating in remote places on your Mac. It could take up a few gigs of your space. The only app that seems to address this problem is CleanMyMac X by MacPaw. It’s loved by many Mac developers because it collects those specific types of development junk, like Xcode or outdated libraries.

Once you launch the app, click on System Junk > Scan. Then, click “Review Details”

CleanMyMac X is a powerful Mac performance improvement app. It makes your Mac as good as new. Let it scan your system and clear out any unwanted Xcode, development and system junk that is taking up too much space and cluttering up your Mac. In a few clicks, your Mac could be running smoother, quicker and more efficiently.

After figuring out a way around the massive breaking change introduced by Xcode 11, it's now time to install Xdebug back on MacOS Catalina.

Update from January 6th 2021:
Using MacOS Big Sur? This solution should work for you too. But since Apple Deprecated PHP in MacOS Big Sur, you should probably rely on Homebrew now.

Update from June 30th 2020:
After some new investigation while trying to upgrade to a newer version of xdebug, I now believe most of the instructions in this post are not necessary. Before doing anything, you should check if xdebug.so already exists in /usr/lib/php/extensions/no-debug-non-zts-20180731/, which I believe is there by default (let me know if otherwise). If it does exist, you could skip to the Enabled support in PHP portion of this post.

Note that building xdebug from source code and actually trying to use that version of xdebug.so (for example by referencing the built file in xdebug/module/xdebug.so after using make install) with the build-in PHP should end up in a 'code signature' error. As described here and here, even after signing the binary, MacOS won't allow system binaries to interact with non-system binaries for security reasons. The only real solution to use a custom version of xdebug would be to compile and use you own instance of PHP instead of the build in one.

Long story short, Apple decided to nuke /usr/include in MacOS Catalina, which has been the default location for C header file for ever in UNIX systems. Trying to install through PEAR / PECL will return an error as the compiler will look for necessary headers file in /usr/include. So the solution is to compile Xdebug manually, manually specifying the actual location of the header files, which are still provided by Xcode, just at a different location.

Xcode

The first step is to get Xcode from the App Store.

Once Xcode installed, we have to get the command line tools :

You might need to actually open Xcode at this point to finish installation and accept terms and conditions, especially if the previous command fails.

Install Xcode 12.5 On Catalina

Finally, make sure the SDK is found. If the path you get differs from the one bellow, you might need to edit the path accordingly later on:

Install Xcode On Catalina

Manually Compiling Xdebug

Getting source

Install Xcode On Catalina

Let's compile 2.7.2, getting the source code from git. Alternatively, you can download the source from Xdebug site.

Install Xcode On Catalina Mac

phpize

Next we need to make a copy phpize so we can edit the include path :

Find this line :

...and replace it with this line :

Run phpize:

You should now see something like this :

Configure & build

We can now configure :

...and run make using our custom SDK location defined as compiler flags. I used a variable to store the path to the SDK so it's easier to edit if it changes :

You might see some warning, just ignore it for now. Finally, we'll need to run :

Again, this command will fail because it can't move the extension to the right place. SIP will prevent it. But no worries, we'll take care of that manually at the next step. make install is still required as it will sign the *.so file.

The above trick should work for any PHP extension you want to compile. If you're trying to compile something other than a PHP extension, I recommend having a look at the Makefile to see which directory to include in your custom CPPFLAGS.

Enabled support in PHP

Once make install has been run, we can move the executable somewhere safe. I use /usr/local/php/extensions.

Then we edit the PHP configuration to enable Xdebug. Simply edit php.ini:

And we add the following at the bottom :

Restart built in server to be sure :

And finally test everything went fine :

If the above command returns nothing, then Xdebug is not available on your install. Go back the steps to find out what's missing.

Install xcode 12.4 on catalina

References and thanks :