Google Git
Sign in
gerrit / buck / refs/heads/github-master
commit69f6cdc89a9ce221484bf20c3a9a9e92ba58fc7c[log] [tgz]
authorGabriel Russo <gabrielrc@fb.com>Fri Dec 06 13:12:38 2019 -0800
committerFacebook Github Bot <facebook-github-bot@users.noreply.github.com>Fri Dec 06 14:06:49 2019 -0800
tree4015cda9b0fe3d791078474c84d92ccd44095c7d
parent12c6c2228131a20013a0e640f8b10dc38f751bd8 [diff]
Bring ProjectFileSystem back to BuildTargetPaths

Summary: we need the filesystem to access .buckconfig info

Reviewed By: stepancheg

shipit-source-id: 19f2eaa953
18 files changed
tree: 4015cda9b0fe3d791078474c84d92ccd44095c7d
  1. .buckconfig
  2. .buckjavaargs
  3. .buckrelease
  4. .editorconfig
  5. .gitattributes
  6. .gitignore
  7. .idea/
  8. .inferconfig
  9. .travis.yml
  10. .watchmanconfig
  11. BUCK
  12. CODE_OF_CONDUCT.md
  13. CONTRIBUTING.md
  14. LICENSE
  15. README.md
  16. android/
  17. appveyor.yml
  18. assets/
  19. bin/
  20. buck-parser-py.iml
  21. buck.iml
  22. build.xml
  23. config/
  24. docs/
  25. jitpack.yml
  26. pmd/
  27. programs/
  28. py/
  29. python-dsl/
  30. scripts/
  31. src-gen/
  32. src/
  33. test/
  34. third-party/
  35. tools/
  36. windows_cxx_support.txt
  37. windows_failures.txt
README.md

Buck

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

Build Status Build status

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://buck.build/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