Re: MACHINE and inc files
On Sun, Jun 21, 2020 at 03:09:40PM +0200, Tomek The Messenger wrote:
The problem which I have is that this one below doesn't work (*):Because there is a misunderstanding on how _<override> works :)
KERNEL_MODULE_AUTOLOAD_velismate += "A"
KERNEL_MODULE_AUTOLOAD += "B"
does not mean that you add A in case of velismate machine is used.
You can have *many* variables that are override-able by machines (or
other OVERRIDES values).
In your example above you will actually have two variables for Yocto
KERNEL_MODULE_AUTOLOAD_velismate = "A"
KERNEL_MODULE_AUTOLOAD = "B"
You can check that by using `-e` after bitbake.
What you want is to **add** to KERNEL_MODULE_AUTOLOAD **only** for
velismate machine. That can be done with:
KERNEL_MODULE_AUTOLOAD_append_velismate = " A"
Note the leading space, and that it's _append_velismate and not
This will just work.
If I have like here (*), so kind of some mix, then kernel-moduleB isn'tAs per KERNEL_MODULE_AUTOLOAD documentation you can actually put it
in the machine configuration file, which makes **a lot** more sense :)
Forget about all your "I'm pulling my hair"-tries and go with that,
But the problem is that my MACHINE is:You want to use MACHINEOVERRIDES for that. Add your 'velismate'
"family" to it (AT THE CORRECT PLACE, use bitbake -e to check, rightmost
in MACHINEOVERRIDES has top priority). You just have to make sure
velismate is in your new machine configuration file.
IIRC, you would need to do:
MACHINEOVERRIDES =. ":velismate"
before all require/include in your machine configuration file.