Xcode-compatible build tool.
Go to file
Grant Paul 57e8d04685 Simplify pre-allocating BOM indexes and BOM tree entries.
Use a single reserve method to reserve space in BOM indexes or in a
BOM tree's entry index, rather than specifying on initialization.
This better supports reserving additional space after allocation,
which is needed in any case, without sacrificing performance.
2016-08-31 17:35:06 -07:00
Libraries Simplify pre-allocating BOM indexes and BOM tree entries. 2016-08-31 17:35:06 -07:00
Specifications Split libraries and specifications into separate install components. 2016-07-05 23:40:21 -07:00
ThirdParty Remove expat dependency, use system libxml2 instead. Fixes #10. 2016-01-27 12:03:06 -08:00
.gitattributes Add notes for GitHub's Linguist tool. 2015-11-04 22:19:26 -08:00
.gitignore Add make project to generate Xcode project. 2016-05-23 17:16:51 -07:00
.gitmodules Remove expat dependency, use system libxml2 instead. Fixes #10. 2016-01-27 12:03:06 -08:00
.travis.linux.trusty.sh Update libpng checksum 2016-08-11 14:54:40 -07:00
.travis.yml Support both ImageIO and libpng for reading PNG images. 2016-07-27 16:18:26 -07:00
CMakeLists.txt Revert "Don't allow installing without a prefix, as this can break systems." 2016-08-08 20:22:52 -07:00
CONTRIBUTING.md Split xcformatter out of xcexecution. 2016-02-29 19:40:40 -08:00
LICENSE Add support for -license option in xcdriver based on the LICENSE file. 2016-06-20 22:17:54 -07:00
Makefile Support make install with PREFIX= in CMake wrapper. 2016-06-16 11:28:17 -07:00
PATENTS Add README, LICENSE, and PATENTS. Move third-party licenses. 2015-11-04 22:22:30 -08:00
README.md Update documentation for required packages on Linux. 2016-08-11 15:52:40 -07:00

xcbuild

xcbuild is an Xcode-compatible build tool with the goal of providing faster builds, better documentation of the build process and running on multiple platforms (in particular OS X and Linux)

Why xcbuild?

Features Performance
🚀Blazing fast incremental buildsxcodebuildxcbuild + Ninja
📖Documents the Xcode build process
🔗Builds Xcode projects and workspaces
🐣Supports Swift apps and frameworksClean Build30.103s25.122s
Tools and libraries for Xcode projects
💝Fully compatible with xcpretty
🎩Uses Ninja and llbuildIncremental Build2.190s0.046s
:octocat:Open source under the BSD license
🐧Builds on Linux

xcbuild and other build tools

xctool Buck xcpretty
xcbuild and xctool are both Xcode-compatible build systems. We plan on slowly deprecating xctool's build support but keep it as a great way to run tests. Facebook's main build system is Buck. Buck has a stronger architecture and advanced features like artifact caching while having a much simpler build format. If you have a new project, it's highly recommended. xcbuild works great with xcpretty. Pipe the output from xcbuild to xcpretty the same way as you would from xcodebuild.

Building

Build Status

  • Xcode 7 or later, on OS X.
  • GCC 4.8 or later, on Linux. libpng16-dev, zlib1g-dev, libxml2-dev, and pkg-config are also required.
  • CMake and Ninja (or llbuild).
    • With Homebrew: brew install cmake ninja
git clone https://github.com/facebook/xcbuild
cd xcbuild
git submodule update --init
make

Build output will be in the build directory. Run xcbuild with ./build/xcbuild.

Usage

The command line options are compatible with xcodebuild.

xcbuild -workspace Example.xcworkspace -scheme Example

Using Ninja (or llbuild)

To switch to the significantly faster Ninja executor:

xcbuild -executor ninja [-workspace Example.xcworkspace ...]

Besides the -executor ninja parameters, the options are otherwise identical. The Ninja executor is fastest if it can avoid re-generating the Ninja files if the build configuration and input project files do not change.

Contributing

xcbuild actively welcomes contributions from the community. If you're interested in contributing, be sure to check out the contributing guide. It includes some tips for getting started in the codebase, as well as important information about the code of conduct, license, and CLA.

Thanks

xcbuild is built on build system documentation from the community. In particular, thanks to these people for their writing:

Third-party licenses are listed in the LICENSE document.