commit | b66898e44d79ef67f856eaeae711bb461564a3c1 | [log] [tgz] |
---|---|---|
author | Peter Schmitt <schmitt@google.com> | Wed May 20 20:03:26 2015 +0000 |
committer | Han-Wen Nienhuys <hanwen@google.com> | Thu May 21 09:50:21 2015 +0000 |
tree | 5adcd55d38a04f5111118e9776317bbfc8e1a914 | |
parent | 9208259df169e46cabdf1102bfc529a915a1581d [diff] |
Allow objc_{library,binary} to depend on cc_library. This is an early version of support for this feature, likely still missing a number of edge cases. However the basic functionality should work. To allow a dependency from objc to cc, the following flags will have to be passed to bazel: --experimental_enable_objc_cc_deps --experimental_disable_java --cpu=ios_i386 --crosstool_top=//tools/objc/crosstool:crosstool The feature is also compatible with --ios_multi_cpus, with the familiar values for --ios_cpu (i386, x86_64, armv7, arm64). However, using this crosstool and any CPU defined in it (legal values are ios_i386, ios_x86_64, ios_armv7, ios_arm64) will make it impossible to use genrules with java make variables in the same build: Obviously they require java support and no that is not available for iOS CPUs. The new flag --experimental_disable_java has not been tested in any circumstances but the one enabled by this CL so use it with caution. This CL does not contain any Xcode support for CC dependencies yet, they will just not show up in the generated Xcode project. -- MOS_MIGRATED_REVID=94116942
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.
How to install Bazel
How to get started using Bazel
The Bazel command line is documented in the user manual
The rule reference documentation is in the build encyclopedia
How to use the query command
How to extend Bazel
The test environment is described in the test encyclopedia
About the Bazel project: