00:05 <khem> yes it did

00:06 <khem> package is not open source sadly

00:07 <khem> I think it could be some change in cargo, I am remembering some discussion somewhere about virtual manifests but cant find it conretely

17:56 <vvn> hi there -- I don't get the difference between BUILDDIR and BDIR. `BUILDDIR=foo . oe-init-build-env` still switches to the default 'build' directory, while `BDIR=foo . oe-init-build-env` works as expected and creates a 'foo' directory, yet only BUILDDIR is documented.

17:57 <vvn> Also, `BDIR=foo/bar/baz . oe-init-build-env` will fail with a message: "Error: The build directory (BUILDDIR) must be set!" if the parent directory foo/bar does not exist, that is very inconsistent.

19:20 <olof> vvn: BUILDDIR is set by oe-init-build-env. It doesn't care about what value it has before. You usually pass your build directory as parameter, but it is not portable to pass parameters when sourcing, BDIR is just be an alternative way to do that.

19:21 <olof> (but it does bypass a check: if you had passed it as a param, you would get an error saying the parent directory doesn't exist.)

19:40 <vvn> ok, that's fine by me. I guess https://docs.yoctoproject.org/singleindex.html#term-BUILDDIR should not be publicly documented then, but BDIR should. That would avoid such confusion.

19:44 <olof> why shouldn't it be?

19:44 <olof> after sourcing the script, you can `echo $BUILDDIR`

19:44 <vvn> ha, good point

19:45 <olof> but BDIR seems like it should be mentioned