755 ${WORKDIR}/rcS.rnd ${D}${sysconfdir}/init.d/rcS
> }
>
> do_install_append_class-release () {
> install -m 755 ${WORKDIR}/rcS.release ${D}${sysconfdir}/init.d/rcS
> }
>
> BBCLASSEXTEND = "production rnd release"
>
> ==
>
> I
In my current project they have defined bbclass files to allow variants of
recipes.
The recipe would then contain do_install_append_XYZ’s for each class.
BBCLASSEXTEND = ”production rnd retail”
would ensure you would get nginx-production, nginx-rnd, nginx-retail ipks.
This way you have one rec
You can create three separate recipes that generate three different nginx
configurations and include one if them in each image recipe.
Best Regards,
Ulf Samuelsson
> 1 juni 2018 kl. 07:46 skrev Damien LEFEVRE :
>
> Hi,
>
> For the same MACHINE I create the following images:
> - myimage-produc
the other two.
BR
Ulf Samuelsson
____
Från: yocto-boun...@yoctoproject.org för
Damien LEFEVRE
Skickat: den 1 juni 2018 13:17:53
Till: Iván Castell
Kopia: Yocto discussion list
Ämne: Re: [yocto] Image specific configuration files
Thanks a lot everyone, this i
Thanks a lot everyone, this is very helpful =)
On Fri, Jun 1, 2018 at 2:14 PM, Iván Castell
wrote:
>
>
> 2018-06-01 11:24 GMT+02:00 Alexander Kanavin :
>
>> I have to say defining multiple distros and then tweaking recipes
>> according to those definitions is not a good practice, as recipes shou
2018-06-01 11:24 GMT+02:00 Alexander Kanavin :
> I have to say defining multiple distros and then tweaking recipes
> according to those definitions is not a good practice, as recipes should
> generally only access DISTRO_FEATURES and otherwise be distro-agnostic. The
> above iptables scenario shou
Yes, much better phrasing:
> A single bitbake invocation always builds a single distro for a specific
target machine
Thanks
On Fri, Jun 1, 2018 at 12:18 PM, Alexander Kanavin
wrote:
> If a build is 'a single bitbake invocation', then yes - it builds for a
> single distro and for a specific tar
If a build is 'a single bitbake invocation', then yes - it builds for a
single distro and for a specific target machine, but it can build multiple
recipes (which includes multiple images, as images are defined with
recipes).
Alex
2018-06-01 13:07 GMT+03:00 Alan Martinovic :
> Hey Alexander,
> y
Hey Alexander,
you seem to have a good understanding on the concepts.
Would you say that:
> A build always builds a single distro
is somewhat of a rule?
On Fri, Jun 1, 2018 at 11:24 AM, Alexander Kanavin
wrote:
> I have to say defining multiple distros and then tweaking recipes
> according
I have to say defining multiple distros and then tweaking recipes according
to those definitions is not a good practice, as recipes should generally
only access DISTRO_FEATURES and otherwise be distro-agnostic. The above
iptables scenario should be handled with different image recipes, which
pull i
You are right, my setup is not able to generate two different images at the
same time. To do that, I setup two different builds sharing the download
directory between them.
2018-06-01 11:11 GMT+02:00 Alan Martinovic :
> Thanks for the replay Iván,
> am I reading correctly that this means that you
Thanks for the replay Iván,
am I reading correctly that this means that you create a single image
file per build
(which can be any of the given types)?
You're setup doesn't allow for building the "developent" and
"production" image at the same time?
Be Well,
Alan
On Fri, Jun 1, 2018 at 11:04 AM
I can provide more details. My custom layer has these files related with
distro:
my_layer/conf/distro/include/common.conf
my_layer/conf/distro/develop.conf
my_layer/conf/distro/production.conf
my_layer/conf/distro/integration.conf
As an example of the previous files,
my_layer/conf
2018-06-01 8:46 GMT+03:00 Damien LEFEVRE :
> For the same MACHINE I create the following images:
> - myimage-production
> - myimage-rnd
> - myimage-retail
>
> The production one has production assisted tools for flashing peripheral HW,
> testing vital HW components, writing some serial numbers, etc
Hey,
would really like to see your example.
Am struggling to get creation of these types of images for a while now.
So far have avoided diving into multiple distros because would like to have
the option
of building all the images at the same time (so they are basically the same
distro).
On Fri, J
I fixed this issue defining different distro.conf files in my custom layer,
adding a custom variable DISTRO_STAGE with the name of my distro
(production, rnd, retail, and so on), Then you setup DISTRO in your
local.conf to the proper value you want to use. Finally you can use that
DISTRO_STAGE vari
16 matches
Mail list logo
