[odb-users] Dependency issue with build2 0.12 and odb 2.5

[Boris Kolpackov]

Vincent <chere.loque at gmail.com> writes:

> So, it seems that calling 'bpkg' in a specific path stills make
> uses/calls of binaries installed at the system level (on the PATH), somehow.
> 
> [...]
>
>    $ ../../build/dev-tools/build2/bin/bpkg create -d . cc config.cxx=g++
> config.cc.coptions=-O3 config.bin.rpath=../local/lib/
> config.install.root=../local --wipe
>    created new configuration in /home/vincent/my_project/_build/odb-build2/
>    $ ../../build/dev-tools/build2/bin/bpkg build --yes --trust-yes
> odb at https://pkg.cppget.org/1/beta
>    added pkg:cppget.org/beta
>    fetching pkg:cppget.org/beta
>    fetching pkg:cppget.org/testing (complements pkg:cppget.org/beta)
>    fetching pkg:cppget.org/stable (complements pkg:cppget.org/testing)
>    error: unable to satisfy constraint (build2 >= 0.11.0) for package odb
>      info: available build2 version is 0.10.0
>    info: while satisfying odb/2.5.0-b.17
> 
> Is there any way to specify a "home path" for build2 binaries?

You could do:

$ PATH="../../build/dev-tools/build2/bin:$PATH" bpkg ...

But there is also --build <path>:

  The build program to be used to build packages. This should be the path to
  the build2 b executable. You can also specify additional options that should
  be passed to the build program with --build-option.[1]

So you can do:

$ ../../build/dev-tools/build2/bin/bpkg --build ../../build/dev-tools/build2/bin/b ...

[1] https://build2.org/bpkg/doc/bpkg-common-options.xhtml