Question or issue on macOS: I was using Xcode 11 (dmg downloaded from developer account extra files section) on mac os 10.14.6. Today i updated my Mac os to 10.15 catalina to use xcode 11 canvas view but the issue is after updating to mac os 10.15 Catalina i am unable to open xcode. Apple just pushed out the official release of Xcode 11. That removes the older macOS SDKs and only includes macOS SDK 10.15. The current version of il2cpp included in Unity only handles up to macOS SDK 10.14.
Question or issue on macOS:
Xcode 11 includes SDKs for iOS 13, iPadOS 13, watchOS 6, macOS 10.15, tvOS 13 and Swift 5.1. Xcode 11 supports running multiple concurrent versions of the Xcode app and of any associated tools. MacOS Catalina 10.15.1 blender 2.8 & 2.81 got display issue Blender Development Ugh, that sounds like a degraded ogl driver Not sure if there is any dev with Catalina 10.15.1 installed (or 10.15 to begin with). I can confirm that gcc builds if I force gmp to build with -fno-stack-check, using Xcode Version 11.2 (11B41) on macOS Catalina 10.15.1 (19B68f). (As a side note, it seems like Xcode 11.2 does not fix the stack alignment issue for gmp, at least not yet.
I was using Xcode 11 (dmg downloaded from developer account extra files section) on mac os 10.14.6
Today i updated my Mac os to 10.15 catalina to use xcode 11 canvas view but the issue is after updating to mac os 10.15 Catalina i am unable to open xcode. When i clicks on xcode icon it jumps for few seconds and then nothing happens.
I have no backup and projects going on and the main thing is that is my office pc where i work. Please help!!
I tried fixing by this but it didn’t helped
I can’t open Xcode project after updating to Catalina
How to solve this problem?
Solution no. 1:
Xcode 11.1 is available on the Mac App Store now so you should probably be using that. Try a force brute approach by deleting Xcode 11, redownload and reinstall.
Solution no. 2:
I was able to work around this by uninstalling Xcode first. What I did:
- Open Finder and navigate to Applications.
- Move Xcode from Applications to Trash.
- In the terminal, run the command
rm -rf ~/Library/Developer - In the terminal, run the command
rm -rf ~/Library/Caches/com.apple.dt.Xcode - Restart your machine.
- Now go to
App Storeand search forXcodeand install it from there.
Solution no. 3:
This works for me.
Close you project then Go to your project file > right click on project_name.xcworkspace > Show Package Contents > delete folder xcsharedata and xcworkspace.
It will create deleted file again once you open that project
Solution no. 4:
One could also try to perhaps add the program to the list of apps allowed to access the disk.
This can be found under: Settings > Security & Privacy > Privacy > ….
Not directly related: but I just did this for the MS Office Programs (Word, Excel, Powerpoint Outlook etc..).
While in contact with MS Support they advised me to delete everything and reinstall. Adding the programs was a lot easier and retained all my data.
Hope this helps!
When you try to build xdebug on macOS Catalina you will get errors like these:
Configure and build xdebug on macOS Catalina
The reason for these errors is that the /usr/include folder is missing because Apple removed it when they released Xcode 11.
But, you can work around this problem. Here is how:
First, you need to make sure that Xcode and the command line tools installed. Open a terminal window and run the following command to display the SDK path:
This command should output something like this:
If not, install the command-line tools with executing:
and follow the instructions. After the installation is finished, start Xcode App to make sure the installation is done.
Now try to display the SDK-Path again:
The php tools needed to compile an extension try to use this missing include folder. We will create a modified version of phpize and php-config which will use the includes from the macOS SDK. First we will copy phpize and php-config and then we will modify these copies with a patch.
We create a new folder in your home directory under /Users/YOUR-USERNAME with the name 'php-private'..
Now copy phpize and php-config to php-private
Now determine which PHP version is installed on your system by executing
You should get something like this
I have prepared two patches to simplify the process. Download the two files and save them in your Downloads folder.
Download the phpize patch phpize-catalina.patch.zip and save it. The contents of the patch file for reference:
For PHP 7.3.9 Download the php-config patch php-config-7.3.9-catalina.patch.zip and save it.
For PHP 7.3.11 Download the php-config patch php-config-7.3.11-catalina.patch.zip and save it.
The contents of the patch file for reference:
Extract the compressed patch files.
PHP 7.3.9:
PHP 7.3.11:
Now we patching our copy of phpize and php-config
PHP 7.3.9:
PHP 7.3.11:
We are ready to compile xdebug
Create a working directory in your home folder. We will build xdebug here
Download xdebug from Xdebug.org and save in under Downloads.
Copy the archive to the working directory and extract it.
Now, we run our patched phpize in the xdebug folder.
When everything went good, you get something like this:
If so, you can skip the next part and continue with configuring and installing Xdebug.
Errors like these means, you need to install some requirements.
If phpize prints lines like these, you need to install autoconf:
To install autoconf, execute the following commands:
Now run our patched phpize in the xdebug folder again.
Check the output, and if everything went good, continue.
Configure and build xdebug:
Now we will find the full path to our patched php-config. This can be done like this:
The output will something like:
Replace '/Users/YOUR-USERNAME/php-private/php-config' with the output of the above command and configure xdebug by executing:
In the output of configure you will see that the SDK path is being used:
Xcode Macos 10.15 Download
Now build the extension
We don't executing 'make install' to install xdebug.so because the macOS System Integrity Protection (SIP) will not allow us to install xdebug to the /usr/lib/extensions folder. To workaround this, we install the extension under the /usr/local folder.
Now edit your php.ini (usually under /etc/php.ini) to load the right xdebug. PHP searches for extensions in its default extension directory. Our xdebug resides outside of this directory, so we have to specify the full path:
Xcode For Macos 10.15.1
To test it, execute:
Xcode Macos 10.15 Update
The output should begin like this:
Restart your apache web server to activate your changes
Comments are closed.