buck

General

Category
Free
Tag
Build Systems
License
Apache License, Version 2.0
Registered
Jul 5, 2014
Favorites
1
Link
http://facebook.github.io/buck
See also
android-cmake
Leiningen
Apache Maven
Gradle
Bazel

Additional

Language
Java
Version
v2018.07.23.01 (Jul 23, 2018)
Created
Apr 17, 2013
Updated
Aug 1, 2018
Owner
Facebook (facebook)
Contributors
Artem Zinnatullin :slowpoke: (artem-zinnatullin)
dpursehouse
Kevin Schultz (krschultz)
Gautam Korlam (kageiit)
rratmansky
asm89
KapJI
sschuberth
grp
jamesgpearce
Zac Sweers (hzsweers)
runningcode
zbsz
shs96c
jbarr21
dcolascione
nguyentruongtho
Sim Sun (simpleton)
Show all (308)308
Activity
Badge
Generate
Download
Source code

Blurb

Buck

Buck is a build tool. To see what Buck can do for you, check out the documentation at http://buckbuild.com/.

Installation

First, clone the Buck repository:

git clone --depth 1 https://github.com/facebook/buck.git
cd buck

Since Buck is used to build Buck, the initial build process involves 2 phases:

1. Bootstrap Buck with ant
git clone --depth 1 https://github.com/facebook/buck.git
cd buck
ant
2. Use bootstrapped version of Buck to build Buck:
./bin/buck build --show-output buck
# output will contain something like
# //programs:buck buck-out/gen/programs/buck.pex
buck-out/gen/programs/buck.pex --help
Prebuilt buck binaries

Pre-built binaries of buck for any buck sha can be downloaded from https://jitpack.io/com/github/facebook/buck/<sha>/buck-<sha>.pex. The very first time a version of buck is requested, it is built via jitpack. As a result, it could take a few minutes for this initial binary to become available. Every subsequent request will just serve the built artifact directly. This functionality is available for any fork of buck as well, so you can fetch https://jitpack.io/com/github/<github-user-or-org>/buck/<sha>/buck-<sha>.pex

Feature Deprecation

Buck tries to move fast with respect to its internals. However, for user facing features (build rules, command line interface, etc), the Buck team tries to have a graceful deprecation process. Note that this generally applies only to documented functionality, or functionality that is less documented, but appears to be in wide use. That process is:

  • An issue is opened on Github suggesting what will be deprecated, and when it will be removed. For larger features that are deprecated, there may be a period when the default is the new setting, and the old behavior may only be used with a configuration change.
  • A change is submitted to Buck that puts the old behavior behind a configuration flag and sets the default to the old behavior. These flags can be found at https://buckbuild.com/concept/buckconfig.html#incompatible.
  • For larger features, a change eventually is put in place that sets the default to the new behavior. e.g. when Skylark becomes the default build file parser.
  • When the removal date is reached, a change is submitted to remove the feature. At this point, the configuration value will still parse, but will not be used by Buck internally.

License

Apache License 2.0