* Overrides for different targets?
@ 2024-12-20 2:39 Stephen Ecker
2024-12-20 7:35 ` Anton Mikanovich
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Ecker @ 2024-12-20 2:39 UTC (permalink / raw)
To: isar-users
[-- Attachment #1.1: Type: text/plain, Size: 1011 bytes --]
Is there a way to set overrides only for specific targets? ...let me
explain my problem:
I have a wks file I use for the base image, and a separate one for
installer. In my installer recipe, I have
WKS_FILE = <my installer file>
but in another kas file loaded for a given option, I am defining an
override
OVERRIDES .= ":my_override"
and
WKS_FILE:my_override = "different wks file"
unfortunately this means that it uses my overridden wks file when this
option is used... In my opinion, the right solution would be to use a
different variable for the installer wks file, unless there's a solution
here I'm not seeing.
Thanks,
Stephen
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/787c5ef4-b99c-4b62-9ff8-8016982ebd14n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1498 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Overrides for different targets?
2024-12-20 2:39 Overrides for different targets? Stephen Ecker
@ 2024-12-20 7:35 ` Anton Mikanovich
0 siblings, 0 replies; 2+ messages in thread
From: Anton Mikanovich @ 2024-12-20 7:35 UTC (permalink / raw)
To: Stephen Ecker, isar-users
20/12/2024 04:39, Stephen Ecker wrote:
> Is there a way to set overrides only for specific targets? ...let me
> explain my problem:
>
> I have a wks file I use for the base image, and a separate one for
> installer. In my installer recipe, I have
> WKS_FILE = <my installer file>
>
> but in another kas file loaded for a given option, I am defining an
> override
>
> OVERRIDES .= ":my_override"
>
> and
>
> WKS_FILE:my_override = "different wks file"
>
> unfortunately this means that it uses my overridden wks file when this
> option is used... In my opinion, the right solution would be to use a
> different variable for the installer wks file, unless there's a
> solution here I'm not seeing.
>
>
> Thanks,
> Stephen
Hello Stephen,
To have "different wks file" value used only for one target you need to set
OVERRIDES .= ":my_override" only for this target (in multiconfig config
file),
while WKS_FILE and WKS_FILE:my_override values can be declared globally
in yaml
(which makes it be copied to local.conf).
Note that you already have ${MACHINE} and ${DISTRO} in default overrides, so
it can be quite enough for target specific settings. See example of
usage in:
meta-test/recipes-core/images/isar-image-ci.bb
But if you only need to set specific WKS_FILE value for installer itself
(not a target), you should use INSTALLER_WKS_FILE variable.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/fb8b8226-41b5-48a9-bdb8-0a72767c7a90%40ilbers.de.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-12-20 7:36 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-12-20 2:39 Overrides for different targets? Stephen Ecker
2024-12-20 7:35 ` Anton Mikanovich
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox