I cloned bazel and this repository. It appears that I can't do a bazel fetch //... against this repository because it appears to shadow the //third_party/jdk from the base_workspace.

ERROR: /home/jeremyje/development/trunk/tools/defaults/BUILD:13:1: no such target '//tools/jdk:GenClass_deploy.jar': target 'GenClass_deploy.jar' not declared in package 'tools/jdk' defined by /home/jeremyje/development/trunk/tools/jdk/BUILD and referenced by '//tools/defaults:genclass'.

Also it's not clear how I use trunk workspace. I'm trying to use a separate workspace that utilize trunk and the base_workspace but it's not clear how to do that. Can you provide an example WORKSPACE file in the docs?

I cloned the repo/submodules and tried to build the examples. It fails quickly with the following error. I am building with bazel 0.3.1rc2, but the same error occurs with 0.3.0. I have not tried earlier bazel versions.

bazel build examples/...:all
trunk/third_party/grpc/grpc_proto.bzl:116:12: Attribute 'attrs' either doesn't exist or uses a select() (i.e. could have multiple values)
Available attributes: $protoc, :action_listener, compatible_with, deprecation, deps, expect_failure, features, gen_cc, gen_java, generator_function, generator_location, generator_name, grpc_cpp_plugin, grpc_java_plugin, has_service, restricted_to, src, tags, testonly, visibility

I encountered this during build:
bazel build examples/...:all
.................
ERROR: No toolchain found for cpu 'armeabi-v7a'.

I am building on x86, why do I need arm?

Some OSX machines have case-insensitive filesystems (as, apparently, mine does). Since both e.g. third_party/gflags/{BUILD,build} exist, git gets terribly confused.

Suggestion - rename the folder to something else :)

Hi,

Looks like somebody created the rules_boost based on your idea and implementation:
https://github.com/nelhage/rules_boost

I've tried that and made it work for a few packages I cared about.

Would like to see rules_boost be pulled back to trunk.

name 'PACKAGE_NAME' is not defined (did you mean 'package_name'?)

See https://code.google.com/p/chromium/issues/detail?id=539853.

WORKSPACE file is no longer compatible with bazel 0.15 version. As maven_jar cannot include "." sign.

Not an issue, but a feature request.

Given the recent changes that moved asan/msan/tsan to using LRTE, I think it would be really nice if the LRTE release would provide msan instrumented libc++ / libstdc++.

While executing: git submodule update --init
I got error for java/commons_logging, java/log4j and libunwind in git clone step.
I changed the repositories in .gitmodules to:
https://github.com/apache/commons-logging.git
https://github.com/apache/log4j.git
https://github.com/llvm-mirror/libunwind.git.

Now I get error in libunwind git clone: server does not allow for unadvertised object...

After I cloned the repo, updated the modules and ran bazel build examples/...:all, I got the following error,

vagrant@vagrant-ubuntu-trusty-64:/trunk$ bazel build examples/...:all
..............................
WARNING: /trunk/tools/build_rules/run_under.bzl:55:14: Argument `cfg = "host"`, `cfg = "data"`, or `cfg = "target"` is required if `executable = True` is provided for a label. Please see https://www.bazel.build/versions/master/docs/skylark/rules.html#configurations for more details.
WARNING: /trunk/tools/build_rules/run_under.bzl:58:12: Argument `cfg = "host"`, `cfg = "data"`, or `cfg = "target"` is required if `executable = True` is provided for a label. Please see https://www.bazel.build/versions/master/docs/skylark/rules.html#configurations for more details.
WARNING: /trunk/tools/build_rules/run_under.bzl:63:11: Variables HOST_CFG and DATA_CFG are deprecated in favor of strings "host" and "data" correspondingly.
WARNING: /trunk/third_party/grpc/grpc_proto.bzl:72:14: Variables HOST_CFG and DATA_CFG are deprecated in favor of strings "host" and "data" correspondingly.
WARNING: /trunk/third_party/grpc/grpc_proto.bzl:77:22: Variables HOST_CFG and DATA_CFG are deprecated in favor of strings "host" and "data" correspondingly.
WARNING: /trunk/third_party/grpc/grpc_proto.bzl:85:23: Variables HOST_CFG and DATA_CFG are deprecated in favor of strings "host" and "data" correspondingly.
WARNING: /trunk/third_party/protobuf/upstream/protobuf.bzl:90:19: Variables HOST_CFG and DATA_CFG are deprecated in favor of strings "host" and "data" correspondingly.
WARNING: /trunk/third_party/protobuf/upstream/protobuf.bzl:96:28: Variables HOST_CFG and DATA_CFG are deprecated in favor of strings "host" and "data" correspondingly.
ERROR: /trunk/examples/asan/BUILD:8:1: in cc_binary rule //examples/asan:leak: non-test target '//examples/asan:leak' depends on testonly target '//third_party/gperftools:tcmalloc_heapcheck' and doesn't have testonly attribute set.
ERROR: Analysis of target '//examples/asan:leak' failed; build aborted.
INFO: Elapsed time: 11.762s

Is there a proper way to use this project? What I do is add my code on top of this project's workspace but there has to be a better way. The bazel workspace instructions are confusing here as well.

I got an error like this:

no such package '@boost//': Error downloading [https://dl.bintray.com/boostorg/release/1.66.0/source  
/boost_1_66_0.tar.gz] to /home/thickey/.cache/bazel/_bazel_thickey/12ea4ca4c5b772e334d238b0acc653b5  
/external/boost/boost_1_66_0.tar.gz: GET returned 403 Forbidden and referenced by ...

I'm not sure if its a local problem or related to hosting.

Mind adding a license? I'd love to use some of them.

Have you seen this? As of the commit in the description, this breaks bazel with a bunch of errors of the pattern

The package third_party/protobuf/upstream is not within the path google/protobuf/internal/descriptor_pool_test1_pb2.py.

This was a commit late last year and remains broken in master.

I don't know if this should be considered an error upstream in that it breaks using the repo as a "subrepo"?

Comments?
Suggestions?

The BUILD rules for this project used to work due to a bug in Bazel: see bazelbuild/bazel#473.

Since these build rules miss a bunch of internal headers, they no longer work.