Google Git
Sign in
gerrit / buck / refs/heads/github-master
commitae2347e05da6f0ef9e0ec21497a654757aca7ad5[log] [tgz]
authorLucas Marçal <Lcsmarcal@users.noreply.github.com>Tue Oct 20 18:41:50 2020 -0300
committerGitHub <noreply@github.com>Tue Oct 20 14:41:50 2020 -0700
tree97d032c2444011948868392129d2b67c6fb14f6d
parent32440f9bb50e802a7671eef5f32a19a76972c319 [diff]
[Apple] Add support to AppClips (#2552)

* Add app clip support

* Add integration test

* fix target name at Integration test

* fix typo

* Fix bundle ProductType

Co-authored-by: Lucas Marçal <lucas.marcal@ifood.com.br>
24 files changed
tree: 97d032c2444011948868392129d2b67c6fb14f6d
  1. .buck-eden-bindmounts
  2. .buckconfig
  3. .buckjavaargs
  4. .buckrelease
  5. .circleci/
  6. .editorconfig
  7. .gitattributes
  8. .gitignore
  9. .idea/
  10. .inferconfig
  11. BUCK
  12. CODE_OF_CONDUCT.md
  13. CONTRIBUTING.md
  14. LICENSE
  15. README.md
  16. android/
  17. assets/
  18. bin/
  19. buck-parser-py.iml
  20. buck.iml
  21. build.xml
  22. config/
  23. docs/
  24. jitpack.yml
  25. pmd/
  26. programs/
  27. py/
  28. python-dsl/
  29. scripts/
  30. src-gen/
  31. src/
  32. test/
  33. third-party/
  34. tools/
  35. windows_cxx_support.txt
  36. windows_failures.txt
README.md

Build Status

Installation

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

1. Clone the Buck repository and bootstrap it with ant:
git clone --depth 1 https://github.com/facebook/buck.git
cd buck
ant

You must be using Java 8 or 11 for this to compile successfully. If you see compilation errors from ant, check your JAVA_HOME is pointing at one of these versions.

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

For buck binaries built for JDK 11, modify end of the url to buck-<sha>-java11.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