Is there any way to load foo.bzl for all BUILD files automatically?

[Ming Zhao]

Essentially I'd like to make some custom macros or skylark rules can
be just used for BUILD files within my workspace. Do I put something
like load(...) in my workspace file?

Thanks.

[Damien Martin-guillerez]

You can put it in a file in tools/build_rules/prelude_bazel and it will be prepended to all your BUILD file in your workspace.

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAN0GiO0uaWTM57rgvw8Q9oGiWj6HK5V_kqjfKbSzgRKpkMaPJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Hu David]

Is this still available?

I would like to include a native rule to all my build files.

I add the native rule to %bazel/tools/build_rules/prelude_bazel file. However, it does not take affect.

Do I miss anything? Thanks.

David

[Kristina Chodorow]

The prelude_bazel file should still work.  You'll need a BUILD file in tools/build_rules/ (it can be empty).

Also, just a note: these are not called native rules.  Native rules are written in Java and compiled into Bazel.  Anything written in Skylark and loaded at runtime is non-native.

--

You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/da93e404-5a55-43f9-bbc1-ed519ef92e5e%40googlegroups.com.

[Hu David]

Thanks! I forget the BUILD file.

[Kristina Chodorow]

The BUILD file actually wasn't a requirement when this thread was originally created: we're gradually moving to referring to .bzl files by label, so the internal load('/tools/build_rules/prelude_bazel') (no BUILD file required) was recently changed to load('//tools/build_rules:prelude_bazel') (where //tools/build_rules has to be a package, i.e., contain a BUILD file).  

On Tue, Dec 1, 2015 at 11:16 PM, Hu David <chi...@gmail.com> wrote:

Thanks! I forget the BUILD file.

--

You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/5b3caf0a-9589-4f8f-b9b9-70bc554a70a3%40googlegroups.com.

[Andrew Allen]

Does this mean that you need to export_files(['prelude_bazel']) in that build file?

/** ~Andrew Z Allen */

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAJdJyYeG9ZVK0o0-VrhW%3DcysS%3D4ZrfgDZqbLG%3DSE%2B93WzTMFWw%40mail.gmail.com.

[Kristina Chodorow]

You don't actually have to.  I don't know whether that's a bug.

[Damien Martin-guillerez]

AFAICT the simple existence of a file define the corresponding label and load statement are not restricted by visibility so I think this work as designed but not necessarly work as intended (but visibility restrictions on load statements are complex, that's why it is not enforced right now).

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAJdJyYf6ROwC%2BHPoUhRkUX2c4Dex0W5SRUoDYFK7xXa9a8xVdg%40mail.gmail.com.