Xcode Not Downloading

Xcode Not Downloading Iphone
Xcode Update Not Downloading
Xcode Not Downloading Windows 10

The malicious Xcode project, dubbed XcodeSpy, installs an EggShell backdoor version on the developer’s macOS computer, which is able to record the victim’s microphone, camera, and keyboard movements, as well as uploading and downloading files.
MacOS Package (.pkg) Installer. The easiest way to install MacPorts on a Mac is by downloading the pkg or dmg for Big Sur, Catalina, Mojave, High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard or Tiger and running the system's Installer by double-clicking on the pkg contained therein, following the on-screen instructions until completion.
If this option is not specified, Git will simply create a new folder named after the remote repository.-recurse-submodules. Clones and initializes all contained submodules. If your project contains submodules, using this parameter will make sure that all submodules will both be cloned and initialized once the main project has been cloned.

Also: Xcode for Windows. Windows 7 ISO Download How To Install Windows 7 Ultimate. After downloading, use a software to make USB Pendrive bootable or use a DVD and burn it to make it bootable.

Quickstart

Install Xcode and the Xcode Command Line Tools
Agree to Xcode license in Terminal: sudo xcodebuild -license
Install MacPorts for your version of the Mac operating system:

Installing MacPorts

MacPorts version 2.6.4 is available in various formats for download and installation (note, if you are upgrading to a new major release of macOS, see the migration info page):

“pkg” installers for Big Sur, Catalina, Mojave, and High Sierra, for use with the macOS Installer. This is the simplest installation procedure that most users should follow after meeting the requirements listed below. Installers for legacy platforms Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard and Tiger are also available.
In source form as either a tar.bz2 package or a tar.gz one for manual compilation, if you intend to customize your installation in any way.
Git clone of the unpackaged sources, if you wish to follow MacPorts development.
The selfupdate target of the port(1) command, for users who already have MacPorts installed and wish to upgrade to a newer release.

Checksums for our packaged downloads are contained in the corresponding checksums file.

The public key to verify the detached GPG signatures can be found under the attachments section on jmr's wiki page. (Direct Link).

Please note that in order to install and run MacPorts on macOS, your system must have installations of the following components:

Apple's Xcode Developer Tools (version 12.2 or later for Big Sur, 11.3 or later for Catalina, 10.0 or later for Mojave, 9.0 or later for High Sierra, 8.0 or later for Sierra, 7.0 or later for El Capitan, 6.1 or later for Yosemite, 5.0.1 or later for Mavericks, 4.4 or later for Mountain Lion, 4.1 or later for Lion, 3.2 or later for Snow Leopard, or 3.1 or later for Leopard), found at the Apple Developer site, on your Mac operating system installation CDs/DVD, or in the Mac App Store. Using the latest available version that will run on your OS is highly recommended, except for Snow Leopard where the last free version, 3.2.6, is recommended.
Apple's Command Line Developer Tools can be installed on recent OS versions by running this command in the Terminal:
Older versions are found at the Apple Developer site, or they can be installed from within Xcode back to version 4. Users of Xcode 3 or earlier can install them by ensuring that the appropriate option(s) are selected at the time of Xcode's install ('UNIX Development', 'System Tools', 'Command Line Tools', or 'Command Line Support').
Xcode 4 and later users need to first accept the Xcode EULA by either launching Xcode or running:
(Optional) The X11 windowing environment for ports that depend on the functionality it provides to run. You have multiple choices for an X11 server:
- Install the xorg-server port from MacPorts (recommended).
- The XQuartz Project provides a complete X11 release for macOS including server and client libraries and applications. It has however not been updated since 2016.
- Apple's X11.app is provided by the “X11 User” package on older OS versions. It is always installed on Lion, and is an optional installation on your system CDs/DVD with previous OS versions.

macOS Package (.pkg) Installer

The easiest way to install MacPorts on a Mac is by downloading the pkg or dmg for Big Sur, Catalina, Mojave, High Sierra, Sierra, El Capitan, Yosemite, Mavericks, Mountain Lion, Lion, Snow Leopard, Leopard or Tiger and running the system's Installer by double-clicking on the pkg contained therein, following the on-screen instructions until completion.

This procedure will place a fully-functional and default MacPorts installation on your host system, ready for usage. If needed your shell configuration files will be adapted by the installer to include the necessary settings to run MacPorts and the programs it installs, but you may need to open a new shell for these changes to take effect.

The MacPorts “selfupdate” command will also be run for you by the installer to ensure you have our latest available release and the latest revisions to the “Portfiles” that contain the instructions employed in the building and installation of ports. After installation is done, it is recommended that you run this step manually on a regular basis to to keep your MacPorts system always current:

At this point you should be ready to enjoy MacPorts!

Type “man port” at the command line prompt and/or browse over to our Guide to find out more information about using MacPorts. Help is also available.

Source Installation

If on the other hand you decide to install MacPorts from source, there are still a couple of things you will need to do after downloading the tarball before you can start installing ports, namely compiling and installing MacPorts itself:

“cd” into the directory where you downloaded the package and run “tar xjvf MacPorts-2.6.4.tar.bz2” or “tar xzvf MacPorts-2.6.4.tar.gz”, depending on whether you downloaded the bz2 tarball or the gz one, respectively.
Build and install the recently unpacked sources:
- cd MacPorts-2.6.4
- ./configure && make && sudo make install
Optionally:
- cd ../
- rm -rf MacPorts-2.6.4*

These steps need to be perfomed from an administrator account, for which “sudo” will ask the password upon installation. This procedure will install a pristine MacPorts system and, if the optional steps are taken, remove the as of now unnecessary MacPorts-2.6.4 source directory and corresponding tarball.

To customize your installation you should read the output of “./configure --help | more” and pass the appropriate options for the settings you wish to tweak to the configuration script in the steps detailed above.

You will need to manually adapt your shell's environment to work with MacPorts and your chosen installation prefix (the value passed to configure's --prefix flag, defaulting to /opt/local):

Add ${prefix}/bin and ${prefix}/sbin to the start of your PATH environment variable so that MacPorts-installed programs take precedence over system-provided programs of the same name.
If a standard MANPATH environment variable already exists (that is, one that doesn't contain any empty components), add the ${prefix}/share/man path to it so that MacPorts-installed man pages are found by your shell.
For Tiger and earlier only, add an appropriate X11 DISPLAY environment variable to run X11-dependent programs, as Leopard takes care of this requirement on its own.

Lastly, you need to synchronize your installation with the MacPorts rsync server:

Upon completion MacPorts will be ready to install ports!

It is recommended to run the above command on a regular basis to keep your installation current. Type “man port” at the command line prompt and/or browse over to our Guide to find out more information about using MacPorts. Help is also available.

Git Sources

If you are developer or a user with a taste for the bleeding edge and wish for the latest changes and feature additions, you may acquire the MacPorts sources through git. See the Guide section on installing from git.

Purpose-specific branches are also available at the https://github.com/macports/macports-base/branches url.

Alternatively, if you'd simply like to view the git repository without checking it out, you can do so via the GitHub web interface.

Selfupdate

If you already have MacPorts installed and have no restrictions to use the rsync networking protocol (tcp port 873 by default), the easiest way to upgrade to our latest available release, 2.6.4, is by using the selfupdate target of the port(1) command. This will both update your ports tree (by performing a sync operation) and rebuild your current installation if it's outdated, preserving your customizations, if any.

Other Platforms

Running on platforms other than macOS is not the main focus of The MacPorts Project, so remaining cross-platform is not an actively-pursued development goal. Nevertheless, it is not an actively-discouraged goal either and as a result some experimental support does exist for other POSIX-compliant platforms such as *BSD and GNU/Linux.

The full list of requirements to run MacPorts on these other platforms is as follows (we assume you have the basics such as GCC and X11):

Tcl (8.4 or 8.5), with threads.
mtree for directory hierarchy.
rsync for syncing the ports.
cURL for downloading distfiles.
SQLite for the port registry.
GNUstep (Base), for Foundation (optional, can be disabled via configure args).
OpenSSL for signature verification, and optionally for checksums. libmd may be used instead for checksums.

Normally you must install from source or from an git checkout to run MacPorts on any of these platforms.

Help

Help on a wide variety of topics is also available in the project Guide and through our Trac portal should you run into any problems installing and/or using MacPorts. Of particular relevance are the installation & usage sections of the former and the FAQ section of the Wiki, where we keep track of questions frequently fielded on our mailing lists.

If any of these resources do not answer your questions or if you need any kind of extended support, there are many ways to contact us!

Technical Note TN2339

This document provides answers to frequently asked questions about command line tools.

What is the Command Line Tools Package?

The Command Line Tools Package is a small self-contained package available for download separately from Xcode and that allows you to do command line development in macOS. It consists of the macOS SDK and command-line tools such as Clang, which are installed in the /Library/Developer/CommandLineTools directory.

Downloading command-line tools is not available in Xcode for macOS 10.9. How can I install them on my machine?

In macOS 10.9 and later, the Downloads pane of Xcode Preferences does not support downloading command-line tools. Use any of the following methods to install command-line tools on your system:

Install Xcode
If Xcode is installed on your machine, then there is no need to install them. Xcode comes bundled with all your command-line tools. macOS 10.9 and later includes shims or wrapper executables. These shims, installed in /usr/bin, can map any tool included in /usr/bin to the corresponding one inside Xcode. xcrun is one of such shims, which allows you to find or run any tool inside Xcode from the command line. Use it to invoke any tool within Xcode from the command line as shown in Listing 1.

Listing 1 Using xcrun to run dwarfdump in the Terminal application.

Download the Command Line Tools package from the Developer website
The Command Line Tools package is available for download on the Download for Apple Developers page. Log in with your Apple ID, then search and download the Command Line Tools package appropriate for your machine such as macOS 10.12 as shown in Figure 1.

Note: In macOS 10.9 and later, Software update notifies you when new versions of the command-line tools are available for update.

Install the Command Line Tools package via the Terminal application
You can install the Command Line Tools package by running the xcode-select --install command.
Note: macOS comes bundled with xcode-select, a command-line tool that is installed in /usr/bin. It allows you to manage the active developer directory for Xcode and other BSD development tools. See its man page for more information.

How can I uninstall the command-line tools?

Xcode includes all of the command-line tools. If it is installed on your system, remove it to uninstall the command-line tools.
If the /Library/Developer/CommandLineTools directory exists on your system, remove it to uninstall the command-line tools.

I have multiple versions of Xcode installed on my machine. What version of Xcode do the command-line tools currently use?

To find out what version of Xcode is being used by your tools, run the following command in Terminal:

Listing 2 Printing the version of Xcode currently used by the command-line tools.

How do I select the default version of Xcode to use for my command-line tools?

To select a default Xcode for your command-line tools, run the following command in Terminal:

where <path/to/> is the path to the Xcode.app package you wish to use for development.

Listing 3 Setting the default Xcode version.

How do I build my projects from the command line?

xcodebuild is a command-line tool that allows you to perform build, query, analyze, test, and archive operations on your Xcode projects and workspaces from the command line. It operates on one or more targets contained in your project, or a scheme contained in your project or workspace. xcodebuild provides several options for performing these operations as seen its man page. xcodebuild saves the output of your commands in the locations defined in the Locations preferences pane of your Xcode application, by default.

See below for various xcodebuild usage. Be sure to navigate to the directory containing your project or workspace in Terminal before running any of the following commands.

To list all schemes in your workspace, run the following command in Terminal:
where <your_workspace_name> is the name of your workspace.

Listing 4 Listing all schemes in the MyApplication workspace.
To list all targets, build configurations, and schemes used in your project, run the following command in Terminal:
where <your_project_name> is the name of your project.

Listing 5 Listing all information about MyProject, an Xcode project.
To build a scheme in your project, run the following command in Terminal:
where <your_scheme_name> and build are respectively the name of your scheme to be built and the action to be performed on your scheme.

Listing 6 Building the tvOS scheme.
Note: xcodebuild supports various build actions such as build, analyze, and archive that can be performed on your target or scheme. However, build is performed by default when no action is specified as shown in Listing 7.
To build your target with a configuration file, run the following command in Terminal:
where <your_target_name> and <your_configuration_file> are respectively the name of your target to be built and the name of your configuration file. See Xcode Help's Build configuration file reference for more information about xcconfig files.

Listing 7 Building the iOS target with a configuration file.
To change the output locations of your xcodebuild command, use the SYMROOT (Build Products Path) and DSTROOT (Installation Build Products Location) build settings that respectively specify a location for your debug products and .dSYM files and one for your released products. See Xcode Help's Build setting reference for more information about these build settings.

Listing 8 Setting up a location for iOS' debug app version.

Listing 9 Setting up a location for iOS's released app version.

My app has multiple build configurations. How do I set a default build configuration for xcodebuild?

In Xcode, the Configurations section of your project's Info pane provides a pop-up menu, which sets the default configuration to be used by xcodebuild when building a target. Use this pop-up menu to select a default build configuration for xcodebuild as seen in Figure 2.

How do I run unit tests from the command line?

xcodebuild provides several options for running unit tests.

To build and run unit tests from the command line, execute the following command in Terminal:

To build unit tests without running them from the command line, execute the following command in Terminal:

To run unit tests without building them from the command line, execute any of the following command in Terminal:

The test action requires specifying a scheme and a destination. See How do I implement the Build For Testing and Test Without Building features from the command line? for more information about build-for-testing and test-without-building actions.

The -workspace option allows you to specify the name of your workspace. Use this option when your scheme is contained in an Xcode workspace.

The -project option allows you to specify the name of your Xcode project. Use this option when your scheme is contained in an Xcode project. It is required when there are multiple Xcode projects in the same directory and optional, otherwise.

The -destination option allows you to specify a destination for your unit tests. It takes an argument <destination-specifier>, which describes the device, simulator, or Mac to use as a destination. It consists of a set of comma-separated key=value pairs, which are dependent upon the the device, simulator, or Mac being used.

The -only-testing and -skip-testing options, which are optional, allow you to run only a specific test and to skip a test, respectively. They take an argument <test-identifier>, which specifies the test to be executed or excluded. test-identifier's format is as follows:

TestTarget, which is required, is the name of the test bundle. TestClass and TestMethod, which are both optional, respectively represent the name of the class and the name of the method to be tested.

Note: See Xcode Scheme and Run your app in Simulator for more information about scheme and destination, respectively.

For macOS apps, destinationspecifier supports the platform and arch keys as seen in Table 1. Both keys are required for running your unit tests in macOS.
Table 1 Supported keys for macOS apps.
Key
Description
Value
platform
The supported destination for your unit tests.
macOS
arch
The architecture to use to run your unit tests.
i386 or x86_64
See Listing 10 for an example that tests a scheme in macOS and where destinationspecifier is set to 'platform=macOS,arch=x86_64'.

Listing 10 Tests the macOS scheme for 64-bit in macOS.

**Table 1** Supported keys for macOS apps.
Key	Description	Value
platform	The supported destination for your unit tests.	macOS
arch	The architecture to use to run your unit tests.	i386 or x86_64

For iOS and tvOS apps, destinationspecifier supports the platform, name, and id keys as seen in Table 2.

**Table 2** Supported keys for iOS and tvOS apps.
Key	Description	Value
platform	The supported destination for your unit tests.	iOS (for iOS apps)tvOS (for tvOS apps)
name	The full name of your device to be used for your unit tests.	The name of your device as displayed in the Devices Organizer in Xcode.
id	The identifier of your device to be used for your unit tests.	See Locate a device identifier for more information about getting your device identifier.

The name and id keys are intergeably used with platform, which is a required key as seen in Listing 11 and Listing 12.

Listing 11 Tests the iOS scheme on a device identified by 965058a1c30d845d0dcec81cd6b908650a0d701c.

Listing 12 Testing the iOSApp scheme on an iPhone.

Listing 13 Do not test iOSAppUITests on an iPhone.

Listing 14 Only testing SecondTestClass' testExampleB in the iOSAppTests unit test.

For iOS Simulator and tvOS Simulator apps, destinationspecifier supports the platform, name, id, and OS keys as seen in Table 3.

**Table 3** Supported keys for iOS Simulator and tvOS Simulator apps.
Key	Description	Value
platform	The supported destination for your unit tests.	iOS Simulator (iOS apps)tvOS Simulator (tvOS apps)
name	The full name of the simulator (iOS simulator for iOS apps and tvOS Simulator for tvOS apps) to be used for your unit tests and as displayed in the run destination of your Xcode project.	The name of your device as displayed in the Devices Organizer in Xcode.
id	The identifier of your device to be used for your unit tests.	See Locate a device identifier for more information about getting your device identifier.
OS	The version of iOS or tvOS to simulate such as 9.0 or the string latest to indicate the most recent version of iOS supported by your version of Xcode.	An iOS version, tvOS version, or latest

The name and id keys are intergeably used with platform, which is a required key as shown in Listing 15 and Listing 16. The OS key is optional.

Listing 15 Tests the iOS scheme on an iPad Pro (12.9 inch) with iOS 10.2 in the Simulator.

Listing 16 Tests the tvOS scheme on an tvOS Simulator identified by D6FA2C2A-E297-406A-AA22-624B4834ACB2.

The -destination option also allows you to run the same unit test on multiple destinations. This is done by adding it multiple times to your xcodebuild test command as demonstrated in Listing 17.

Listing 17 Tests the iOS scheme in both the Simulator and on an iPod touch.

Note: xcodebuild runs your tests sequentially. For instance In Listing 17, xcodebuild will first test iOS in the Simulator before executing it on the iPod touch.

How do I implement the Build For Testing and Test Without Building features from the command line?

xcodebuild provides the build-for-testing action for Xcode's Product > Build For > Testing feature. You must specify a scheme to use it. To use it, execute the following command in Terminal:
See How do I run unit tests from the command line? for more information about xcodebuild build-for-testing's options.

Listing 18 Builds tests and associated targets in the tvOS scheme using the tvOS Simulator identified by D6FA2C2A-E297-406A-AA22-624B4834ACB2.
build-for-testing generates an xctestrun file, which is saved in the derived data folder. See xcodebuild.xctestrun's man page for more information about xctestrun files.
xcodebuild provides the test-without-building action for Xcode's Product > Perform Action > Test Without Building feature. test-without-building requires that you specify either a scheme or an xctestrun file.
- Usage when using a scheme
  See How do I run unit tests from the command line? for more information about xcodebuild test-without-building's options.
  Important: When using a scheme, test-without-building searches for bundles in the build root (SYMROOT). Therefore, be sure to build your target or that your build root includes the bundles to be tested before running this command. See Xcode Help's Build settings reference for more information about SYMROOT.
  
  Listing 19 Tests the iOSApp scheme on an iPhone SE with iOS 10.1 in the Simulator.
- Usage when using an xctestrun file
  where <your_xctestrun_name> is the name of the file containing your test run parameters. See xcodebuild.xctestrun' s man page for more information about xctestrun files. See How do I run unit tests from the command line? for more information about the other options.
  Important: When using an xctestrun file, test-without-building searches for bundles at paths specified in the file. Therefore, be sure that the bundles exist at the specified paths before running this command.
  
  Listing 20 Testing bundles and other parameters specified in iOSApp_iphonesimulator.xctestrun using the iOS Simulator identified by 6DC4A7BA-EA7F-40D6-A327-A0A9DF82F7F6.
  
  Listing 21 Tests everything but iOSAppUITests specified in iOSApp_iphonesimulator.xctestrun using the iOS Simulator identified by 3D95DF14-E8B7-4A05-B65B-78F381B74B22.

Note:build-for-testing and test-without-building provide support for continuous integration systems.

What keys can I pass to the exportOptionsPlist flag?

To get all available keys for -exportOptionsPlist, run the following command in Terminal:

Listing 22 Fetching all keys supported by -exportOptionsPlist.

See Figure 3 for a sample file that contains some options for the -exportOptionsPlist flag.

How do I archive and export my app for distribution?

To archive and export your app for distribution, run the following command in Terminal:

where <xcarchivepath> specifies the archive or the path of the archive to be exported, <destinationpath> specifies where to save the exported product, and <path> is the path to the file with a list of options for the -exportOptionsPlist flag.

Listing 23 Exports the iOSApp archive to the Release location with the options saved in the OptionsPlist.plist.

Document Revision History