commit | aa3b5a9d57107bf87e0d2efd2823f9d683b12828 | [log] [tgz] |
---|---|---|
author | Peter Schmitt <schmitt@google.com> | Wed Feb 25 22:54:19 2015 +0000 |
committer | Han-Wen Nienhuys <hanwen@google.com> | Wed Feb 25 22:54:19 2015 +0000 |
tree | 6529438b7e9e4dca9ccb4b8c7899978246d83509 | |
parent | 1be297726e7cc1280bf4e4fe63b491de8dd0c4db [diff] |
Introduce ios_application rule. In this, its first incarnation this rule provides no new functionality - all it does is take an objc_binary and perform any bundling the objc_binary would have done anyhow. This will allow us to remove bundling functionality from objc_binary and add multi-architecture transitions between ios_application and objc_binary. However, I did remove the requirement for the infoplist attribute on bundles. We don't actually need it (a plist is generated automatically) and this removal makes the transition much easier. RELNOTES: Introduce ios_application_rule. -- MOS_MIGRATED_REVID=87194403
Bazel is very much a work in progress. We'd love if you tried it out, but there are many rough edges. Please feel free to give us feedback!
{Fast, Correct} - Choose two
Bazel is an build tool that builds code quickly and reliably. It executes as few build steps as possible by tracking dependencies and outputs, controls the build environment to keep builds hermetic, and uses its knowledge of dependencies to parallelize builds.
This README file contains instructions for building and running Bazel.
Supported platforms:
Java:
Clone the Bazel repo from GitHub:
$ cd $HOME $ git clone https://github.com/google/bazel/
To build Bazel on Ubuntu:
Install required package:
$ sudo apt-get install libarchive-dev
Build Bazel:
$ cd bazel $ ./compile.sh
Using Bazel on Mac OS X requires:
To build Bazel on Mac OS X:
Install required packages:
$ port install protobuf-cpp libarchive
or
$ brew install protobuf libarchive
Build Bazel:
$ cd bazel $ ./compile.sh
The Bazel executable is located at <bazel_home>/output/bazel
.
You must run Bazel from within a workspace directory. Bazel provides a default workspace directory with sample BUILD
files and source code in <bazel_home>/base_workspace
. The default workspace contains files and directories that must be present in order for Bazel to work. If you want to build from source outside the default workspace directory, copy the entire base_workspace
directory to the new location before adding your BUILD
and source files.
Build a sample Java application:
$ cp -R $HOME/bazel/base_workspace $HOME/my_workspace $ cd $HOME/my_workspace $ $HOME/bazel/output/bazel build //examples/java:hello-world
Note: on OS X, you must specify --cpu=darwin to build Java programs (e.g., bazel build --cpu=darwin //examples/java:hello-world).
The build output is located in $HOME/my_workspace/bazel-bin/examples/java/
.
Run the sample application:
$ $HOME/my_workspace/bazel-bin/examples/java/hello-world