Install the smallest Apple developer environment that satisfies the course. The standalone Command Line Tools package is usually enough when a course needs UNIX tools, Git, Clang, or a Homebrew prerequisite but does not require the Xcode application, Apple-platform SDK workflows, simulators, or an Xcode project. Verify what is active instead of treating a successful installer dialog as the result.
If you arrived here because Homebrew requested developer tools, preserve the installer message and first review the App Store and Homebrew responsibility boundary. This article installs only Apple’s developer base; it does not install Homebrew.
Decide between Command Line Tools and Xcode
Use the course documentation as the authority:
| Requirement | Likely choice |
|---|---|
| Shell tools, Git, Clang, headers, or Homebrew prerequisite | Standalone Command Line Tools may be sufficient |
| Build or submit an Xcode project | Full Xcode |
| Use Apple-platform simulators or Xcode’s interface | Full Xcode and required components |
| A named Xcode version or SDK | The exact compatible Xcode environment |
| Requirement is unclear | Stop and ask the instructor or course support |
Apple’s Command Line Tools installation guide describes the standalone package as an alternative to full Xcode for work outside Xcode. The package includes an SDK, manual pages, and toolchain binaries, but some commands and platform components require full Xcode.
Installing both does not remove the need to know which developer directory is active.
Inspect the current state first
Run:
xcode-select --print-path
A configured standalone installation normally reports:
/Library/Developer/CommandLineTools
A full Xcode selection may report an Xcode developer directory instead. An error is evidence that no active developer directory is currently selected; it does not prove that every related file is absent.
Check for the standalone package receipt:
pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
Apple documents this exact receipt query for checking the installed package version. Record the version and install time if present.
If a course requires full Xcode, stop here and follow its documented version and component procedure. Do not switch developer directories merely to make this article’s example match.
Request the standalone installation
When the course decision supports the standalone package and inspection shows it is needed, run:
xcode-select --install
Apple documents that this command requests installation and opens a system dialog. Read the dialog and license agreement, confirm that the request came from your action, and complete the Apple installer.
A fresh macOS installation may also prompt for the tools when you first invoke a
developer command such as git. Starting with xcode-select --install keeps
the dependency explicit.
Do not download an unofficial package, run a deletion command, or change a managed Mac to bypass an institutional restriction. If the prompt says the tools are already installed or no compatible software is available, preserve the exact message and return to inspection or official support.
Verify three independent facts
Open a new Terminal window after installation.
First, verify the selected developer directory:
xcode-select --print-path
Second, verify the package receipt and version:
pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
Third, ask the active developer environment to locate Clang, then run it:
xcrun --find clang
clang --version
Record the paths and version output. These checks answer different questions: selection, installed package identity, command resolution, and executable behavior.
If the course requires Git, also inspect:
xcrun --find git
git --version
Do not configure Git identity, SSH keys, language runtimes, or editor extensions yet. Those responsibilities belong to the next course-toolchain setup.
Check updates after macOS changes
Apple says Command Line Tools updates are offered through Software Update or
the softwareupdate command when compatible with the installed macOS. After a
macOS upgrade, recheck for a compatible Command Line Tools release and rerun the
verification commands.
Do not hard-code one Xcode or Clang version as universally current. Course requirements, macOS compatibility, and Apple’s releases change.
Diagnose by evidence
| Observation | Next question |
|---|---|
xcode-select reports no active directory |
Is the standalone package or Xcode required and installed? |
| Active path points into Xcode | Does the course intend full Xcode? |
| Package receipt exists but selection differs | Which developer directory should be active? |
xcrun --find clang fails |
What selection or installation message was reported? |
| Homebrew reports outdated tools | Which compatible Apple update is offered? |
| Managed Mac blocks installation | Which institutional process supplies the tools? |
Do not “repair” these states with recursive deletion. Apple’s developer documentation includes removal procedures, but removal is a separate, destructive troubleshooting decision that requires evidence, backup, and a specific reason.
Complete the installation record
## Xcode Command Line Tools record
- Course requirement:
- Choice: standalone Command Line Tools | full Xcode | unresolved
- Starting `xcode-select` result:
- Installation method and message:
- Active developer directory:
- Package version:
- `xcrun --find clang` result:
- `clang --version` result:
- Software Update status:
- Restriction or unresolved issue:
For the minimum first pass, complete Course requirement, Choice, Active developer directory, Package version, and Restriction or unresolved issue. Complete installation-message and compiler fields when an installation is needed or already exists.
Common mistakes
- Installing full Xcode when the course needs only command-line tools.
- Assuming Homebrew is a substitute for Apple’s developer tools.
- Treating the first
gitprompt as an unexplained failure. - Verifying only that an installer finished.
- Switching the developer directory without recording the previous path.
- Copying deletion commands to fix a selection problem.
- Ignoring tool compatibility after a macOS upgrade.
Do this now
Write the course requirement, inspect the current selection and package receipt, then install only if the decision and authority are clear. Complete all applicable verification fields. If the requirement remains unclear, record the question for the instructor instead of installing both environments.
Log what you learned
The Xcode Command Line Tools record is the learning log. Save the selected developer directory, package evidence, command resolution, verification result, and any unresolved requirement there.
If the previous article deferred Homebrew only because developer tools were missing, return now to install and verify the selected Homebrew item. Otherwise, continue directly to the course environment.
Next, use the verified base to set up Git, SSH, and only the toolchains your course requires.