On 2017-05-08 14:31, Kristina Chodorow wrote:
> The one bug I notice is @//foo.bzl doesn't have a colon, but it's unlikely
> you have a package named foo.bzl.
Eh, that's a red herring... my actual .bzl is named something different
and *does* have a ':' in the `load`. (Also, it is surely loading `debug`
or it would be complaining about that...)
> But it works for me regardless:
>
> $ bazel build //:foo
> WARNING: /home/kchodorow/test/a/foo.bzl/foo.bzl:2:3: This rule does nothing.
> INFO: Found 1 target...
> Target //:foo up-to-date (nothing to build)
> INFO: Elapsed time: 0.261s, Critical Path: 0.00s
>
> So, what version of bazel are you running (`bazel version`), what system
> are you on, any other info you could give about your setup?
Build label: 0.4.5- (@non-git)
Build target:
bazel-out/local-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Wed Apr 5 15:28:13 2017 (1491406093)
Build timestamp: 1491406093
Build timestamp as int: 1491406093
Fedora 25
I am actually trying to implement some new stuff in
http://github.com/robotlocomotion/drake. There are other custom rules
that work (e.g. generate_export_header, drake_generate_file), but for
some reason I can't get new ones to work, even directly invoking the
target (`bazel build @package//:foo`).
Is it something to do with being in an "external" package?
--
Matthew