<richard.purdie@...> wrote: > The intent is the user could add something like: > > require conf/yocto-autobuilder/x32.inc > > or > > require conf/yocto-autobuilder/multilib-mipsn32

id=14462 * several things don't build within the eSDK, e.g. ovmf, multilib, lttng, gstreamer-plugins-good I've put off fixing some elements as I've hoped that if we fixed the layer

We use OVERRIDES in a number of interesting places, including within multilib configurations for the tune-XXX variable suffixes.

Hi all, I still had a couple of ¢ to give so here they are. I summoned the Google god and I found this stackoverflow on how to execute multiple lines instead of the one eval is expecting: https://stac

Hi all, Giving my 2¢. Indeed, and the thing is... it does not fix the original issue, so third party layers not doing that will still have the same bug which is hard to detect. Since we can't unforce

However the https://sourceware.org/glibc/wiki/ABIList is ignored in case of multilib or usrmerge structure of the image's rootfs.

I was trying to avoid anything too complex to parse.... but I wonder if we can enlist the help of the python interpreter. If we have an appropriate delimiter, something like this might work: def apply

Not that I see at the moment. Only for native/nativesdk/multiconfig (anything using the class extension code). Cheers, Richard

Out of curiosity, do you anticipate that this will be used for any part of the implementation of multiconfig as well? Chris

dep.endswith(("-native", "-native-runtime")) or ('nativesdk-' in dep) or ('cross-canadian' in dep) or ('-crosssdk-' in dep): return dep else: # Do not extend for that already have multilib

The multilib class exists mainly as we didn't want to go through every recipe and mark things up that way, believing instead the code could automate it.

Of the two I think using `${PN}` is the correct one otherwise you'd get a clash between the package names when building with multilib (so you get `X-bar` and `lib32-X-bar` for example

<richard.purdie@...> wrote: Continuing the discussion from the OE TSC meeting, now that I've had a little time to digest the idea: I don't think the filter functions are necessarily a

python runs after multilib so must use MLPREFIX in changes.

Using a multilib configuration you would have something like: build (build directory) conf local.conf: MACHINE = "genericx86_64" DISTRO = "poky" BBMULTICONFIG = "container1 containter2

There's already several variations on the AB which are not stock poky or poky-lsb (api docs, multilib, systemd, etc), so lets just build variations of Poky. Ross

[...] baselib has never worked with a subdirectory, we struggled to get multilib to work at all, let alone adding in that subset of problems.

No - fail with a conflict Yes - continue Is multilib resolution enabled?

There have been musl, multilib, tiny, systemd and other issues but I believe these to be resolved. Thanks also go to Paul for fixing devtool to work with this.

Execution of these targets would likely be in the form "bitbake multiconfig:configA:core-image-minimal core-image-sato" so similar to our virtclass approach for native/nativesdk/multilib