Re: [yocto] Defining group of machines
> > is that what you were after? > override is the first thing that crossed my mind... Thanks both of you, an additional machine override was exactly what we needed. Best regards, Olli -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Defining group of machines
Bonsoir, > > > We’ve a product group with different devices, each having their > > > machine-conf, eg > > > > > > Device_a > > > > > > Device_a_mini > > > > > > Device_b > > > > > > Device_b_mini <- Upcoming > > > > > > Device_c <- Upcoming > > i know i did this once upon a time using the MACHINEOVERRIDES > > variable to "insert" a machine family into the sequence of machine > > definitions. as long as there is (i believe) a strictly hierarchical > > grouping of machines you want to define, i'm pretty sure > > MACHINEOVERRIDES is what you want. > > > > let me see if i can find where i did that once. > > yeah, i'm pretty sure you want MACHINEOVERRIDES: > > https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-MACHINEOVERRIDES > > which has a nice example of how to invent a new "machine" category > (qemuall) that subsumes a number of actual qemu machines. is that what > you were after? override is the first thing that crossed my mind... In addition to override, include file (xxx.inc) and use of require/include directive might help wrt. to configuration files. -- Cheers! Loic -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Defining group of machines
On Fri, 3 May 2019, Robert P. J. Day wrote:
> On Fri, 3 May 2019, Westermann, Oliver wrote:
>
> > We’ve a product group with different devices, each having their
> > machine-conf, eg
> >
> > Device_a
> >
> > Device_a_mini
> >
> > Device_b
> >
> > Device_b_mini <- Upcoming
> >
> > Device_c <- Upcoming
> >
> > Since device_a and device_a_mini share a lot of code, for them we
> > use one of the machine overrides, describing the processor family,
> > so I use RDEPENDS_${PN}_append_device_a if I just need it for
> > device_a and RDEPENDS_${PN}_append_am57x for device_a and
> > device_a_mini.
> >
> > Now I’m in the situation that device_c will use the same CPU as
> > device b, so I need something like a “group” of devices for family
> > b.
> >
> > How can I define a MACHINE_GROUP_device_b_group = “device_b
> > device_b_mini” so I can do
> >
> > RDEPENDS_${PN}_append_device_b_group or
> > do_install_append_device_b_group()?
>
> i know i did this once upon a time using the MACHINEOVERRIDES
> variable to "insert" a machine family into the sequence of machine
> definitions. as long as there is (i believe) a strictly hierarchical
> grouping of machines you want to define, i'm pretty sure
> MACHINEOVERRIDES is what you want.
>
> let me see if i can find where i did that once.
yeah, i'm pretty sure you want MACHINEOVERRIDES:
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-MACHINEOVERRIDES
which has a nice example of how to invent a new "machine" category
(qemuall) that subsumes a number of actual qemu machines. is that what
you were after?
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Defining group of machines
On Fri, 3 May 2019, Westermann, Oliver wrote:
> We’ve a product group with different devices, each having their
> machine-conf, eg
>
> Device_a
>
> Device_a_mini
>
> Device_b
>
> Device_b_mini <- Upcoming
>
> Device_c <- Upcoming
>
> Since device_a and device_a_mini share a lot of code, for them we
> use one of the machine overrides, describing the processor family,
> so I use RDEPENDS_${PN}_append_device_a if I just need it for
> device_a and RDEPENDS_${PN}_append_am57x for device_a and
> device_a_mini.
>
> Now I’m in the situation that device_c will use the same CPU as
> device b, so I need something like a “group” of devices for family
> b.
>
> How can I define a MACHINE_GROUP_device_b_group = “device_b
> device_b_mini” so I can do
>
> RDEPENDS_${PN}_append_device_b_group or
> do_install_append_device_b_group()?
i know i did this once upon a time using the MACHINEOVERRIDES
variable to "insert" a machine family into the sequence of machine
definitions. as long as there is (i believe) a strictly hierarchical
grouping of machines you want to define, i'm pretty sure
MACHINEOVERRIDES is what you want.
let me see if i can find where i did that once.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Defining group of machines
Hey,
We've a product group with different devices, each having their machine-conf, eg
Device_a
Device_a_mini
Device_b
Device_b_mini <- Upcoming
Device_c <- Upcoming
Since device_a and device_a_mini share a lot of code, for them we use one of
the machine overrides, describing the processor family, so I use
RDEPENDS_${PN}_append_device_a if I just need it for device_a and
RDEPENDS_${PN}_append_am57x for device_a and device_a_mini.
Now I'm in the situation that device_c will use the same CPU as device b, so I
need something like a "group" of devices for family b.
How can I define a MACHINE_GROUP_device_b_group = "device_b device_b_mini" so I
can do
RDEPENDS_${PN}_append_device_b_group or do_install_append_device_b_group()?
Best regards, Olli
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
