Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Build scripts and configuration for use across all Wincent projects
Shell Ruby Perl CSS

Apply changes for ARC-compatibility

Signed-off-by: Greg Hurrell <>
latest commit 72a011ea2f
@wincent authored
Failed to load latest commit information.
help Remove evil BOM from help.tmpl Switch to BSD license Switch to BSD license Switch to BSD license
LICENSE.txt Switch to BSD license Switch to BSD license Switch to BSD license
README.txt README: update for Snow Leopard handle first release Switch to BSD license Switch to BSD license Switch to BSD license Switch to BSD license Switch to BSD license
UpdateGitRevisionNumbers.rb Switch to BSD license Switch to BSD license Switch to BSD license
base-style.xcconfig Apply changes for ARC-compatibility
cocoa-app-target.xcconfig Switch to BSD license
debug-style.xcconfig Remove ZERO_LINK setting, as it is long since dead Initial import
foundation-tool-target.xcconfig Switch to BSD license
framework-target.xcconfig Update copyright year range
git.rb Switch to BSD license
interface-builder-palette.xcconfig Switch to BSD license
loadable-bundle-target.xcconfig Switch to BSD license
loadable-test-bundle-target.xcconfig Switch to BSD license
pref-pane-target.xcconfig Switch to BSD license
release-style.xcconfig Remove another legacy setting



The Wincent Buildtools (from here on referred to as "buildtools") is a
collection of scripts, tools and configuration files used in the build
processes of a number of Wincent products (for a full product listing see buildtools is licensed under the simplified BSD
license (see the file, LICENSE.txt).

I maintain these tools as a separate package for two reasons: firstly, because
they allow frequently-used tools and configuration information to be stored in
a central location rather than replicated across projects, and secondly,
because I wanted to release the source code to some software I was developing
under the GPL (specifically, WOTest; see:, so it made
sense to release the toolset required to build the software under the same

There are two non-standard executables that some buildtools scripts depend on
(they expect to find them in the PATH), "wincent-strings-util" and
"wincent-icon-util". The former, Wincent Strings Utility, is a separate
project, licensed under the GPL. More information can be obtained from the
project website: The latter, Wincent Icon Utility,
is also a separate project licensed under the GPL but there is no project
website for it at the moment.


The official buildtools Git repository can be cloned using:

  git clone git://

A web-based repository browser can be explored at:

At the time of writing, there are three branches in the repository:

  - master: cutting edge development corresponding to the latest version of Mac
    OS X (currently Mac OS X 10.6 Snow Leopard)
  - maint: stable development line, usually only a few commits behind "master"
  - leopard: maintenance branch, unlikely to receive many updates

As buildtools serves as support for other products, buildtools "releases" as
such are never tagged. You will, however, find tags such as "Synergy-3.5a5"
which are used to record which version of buildtools was used to build the
other product.


These buildtools are provided free of charge under the terms of the BSD
license. If they are useful to you please consider visiting the website and
making a donation:


The purpose and operation of most of the scripts are self-explanatory. The
scripts have been designed for use with Wincent projects and require a specific
filesystem layout (as described below). Use with Wincent projects should be
straightforward; use in other contexts may require modifications to be made.


These buildtools are designed to work with multiple projects sharing a common
directory structure, including a shared built products directory and a shared
build intermediates directory. The base layout used by Wincent consists of the
following directories at the topmost level:


Project folders also sit at the topmost level. Most Wincent products use the
following layout for project folders:


Files checked out from the repository (generally all those necessary to build
the project) are stored in the "src" subdirectory. All other ancillary
materials (generally nothing necessary to build the project), if any, are
stored in the "extra" subdirectory.

The buildtools themselves are generally included in each project via the Git
submodule mechanism, inside the "src" folder for the project:


This layout ensures that all projects have the same relative paths to the build
and build-intermediates directories; that is, from the "src" directory of each
project the relative paths are:



Wincent Colaiuta                 (company website)                (personal weblog)  (contact page)
Something went wrong with that request. Please try again.