commit | 69f6cdc89a9ce221484bf20c3a9a9e92ba58fc7c | [log] [tgz] |
---|---|---|
author | Gabriel Russo <gabrielrc@fb.com> | Fri Dec 06 13:12:38 2019 -0800 |
committer | Facebook Github Bot <facebook-github-bot@users.noreply.github.com> | Fri Dec 06 14:06:49 2019 -0800 |
tree | 4015cda9b0fe3d791078474c84d92ccd44095c7d | |
parent | 12c6c2228131a20013a0e640f8b10dc38f751bd8 [diff] |
Bring ProjectFileSystem back to BuildTargetPaths Summary: we need the filesystem to access .buckconfig info Reviewed By: stepancheg shipit-source-id: 19f2eaa953
Buck is a build tool. To see what Buck can do for you, check out the documentation at http://buck.build/.
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:
git clone --depth 1 https://github.com/facebook/buck.git cd buck ant
./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
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
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:
Apache License 2.0