tree 080e0e3889836c07b7589ef8cd04c135062cc839
parent 9cdb70b93bcbb6e1e1575537546cb7f2cc6a4641
author Dan Willemsen <dwillemsen@google.com> 1437782007 -0700
committer Dan Willemsen <dwillemsen@google.com> 1442270112 -0700

Implement plugins for bootstrap go modules

Now that we have multi-stage bootstrapping, we can make the primary
builder build more dynamic. Add the concept of plugins that will be
linked and loaded into bootstrap_go_binary or bootstrap_go_package
modules. It's expected that the plugin's init() functions will do
whatever registration is necessary.

Example Blueprint definition:

    bootstrap_go_binary {
      name: "builder",
      ...
    }

    bootstrap_go_package {
      name: "plugin1",
      pluginFor: ["builder"],
    }

A package may specify more than one plugin if it will be inserted into
more than one go module.

Change-Id: I109835f444196b66fc4018c3fa36ba0875823184