Virtual packages

[Shakeel Mahate]

I am trying to understand some of the "virtual packages" referred to in BUILD files such as //conditions //build //tools etc

Is there a list of all of these "virtual packages", searching for this term on https://docs.bazel.build/search.html?cx=012346921571893344015%3Axv_nfgpzbu4&cof=FORID%3A10&ie=UTF-8&q=virtual+package did not yield any significant results. 

[Damien Martin-Guillerez]

There is no such list I believe.

//tools is not a virtual package. The list I can remember is

   //tools/defaults <-- some default late bound labels (e.g. //tools/defaults:jdk)

   //external <-- external bindings

   //conditions: default conditions

 

On Wed, Nov 1, 2017 at 3:12 PM Shakeel Mahate <shakeel...@gmail.com> wrote:

I am trying to understand some of the "virtual packages" referred to in BUILD files such as //conditions //build //tools etc

Is there a list of all of these "virtual packages", searching for this term on https://docs.bazel.build/search.html?cx=012346921571893344015%3Axv_nfgpzbu4&cof=FORID%3A10&ie=UTF-8&q=virtual+package did not yield any significant results. 

--
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/1fdc7ace-3e8c-4a14-802b-81d938cac148%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Shakeel Mahate]

So what is a name for these special things, "tools externals condition". They simply show up in the user manual and in examples in the docs. The docs which describes //external refers to it as a virtual package.

What happens if you have a folder in your WORKSPACE that matches that name?

Is there a reason why they are prefixed with // and not to some other prefix, such as @ or # or something else?