Build all packages of a multiPackage at once

[icedieler]

I have defined a nested multiPackage structure in my top-level recipe foo.yaml. It looks a little bit like this:

multiPackage:
  "":
    environment:
      CONFIG_VARIANT: "base"

    buildVars: [CONFIG_VARIANT, CONFIG_TARGET]
    buildScript: |
      echo "{CONFIG_VARIANT} build" > ${CONFIG_VARIANT}-done.txt

    multiPackage:
      tgt_1:
        environment:
          CONFIG_TARGET: "tgt_1"

        buildVars: [CONFIG_TARGET, CONFIG_VARIANT]
        buildScript: |
          echo "${CONFIG_VARIANT}-${CONFIG_TARGET} build" > done.txt

      tgt_2:
        environment:
          CONFIG_TARGET: "tgt_2"

        buildVars: [CONFIG_TARGET, CONFIG_VARIANT]
        buildScript: |
          echo "${CONFIG_VARIANT}-${CONFIG_TARGET} build" > done.txt

My question is how I can build foo-tgt_1 and foo-tgt_2 with a single invocation of bob. bob dev ... foo-tgt_1 works fine but bob dev ... foo gives me the error

Error: Package '/foo' not found

[rhubert]

you should be able to use the a simple wildcard in this case:

bob dev //foo*

(depending on your shell you might need to escape or quote the asterisk)

It's also possible to use xpaths to specify which package you want to select. See https://bob-build-tool.readthedocs.io/en/latest/manpages/bobpaths.html for more details

[jkloetzke]

To be precise, //foo* would select any package with the prefix foo, at any depth in the dependency graph. For example, it would also match /baz/foobar if that would exist. So in this specific example, I would suggest to use /foo-* (or even shorter foo-*) to match the desired packages more closely.

[icedieler]

Thanks! That was really helpful.