Re: [yocto] Usage of yocto on different (production vs debug) scenarios

Hello again forum. I plan using a PR service on different build scenarios (i.e. development, production). I think the right way to proceed is running a different PR server instance listening on a different port for each scenary. So, a PR server instance listening on port X for development and

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

That sounds really convincing, I will give it a chance and come back to describe the hole process after all. Thank you for that valuable information Mr. Ross 2018-04-23 17:38 GMT+02:00 Burton, Ross : > Very curious as to what book said that, because *any* example of that >

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

Thanks Ross for your answers. I'm still working on fully understanding shared state so I appreciate your help. Let me follow up on both your answers in a single message. On Mon, Apr 23, 2018 at 6:38 PM, Burton, Ross wrote: > On 23 April 2018 at 16:23, Iván Castell

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

Very curious as to what book said that, because *any* example of that happening is a bug in the recipe itself. I wouldn't listen to it: the YP autobuilder has a shared sstate for three distributions * four architectures * two libc implementations and doesn't have problems. Ross On 23 April 2018

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

Thanks a lot for all your replies. I am working on a solution trying to get the best option of all your answers. I will come back after deciding my solution to share it with the community. Related with that shared state cache, I found some information on a e-book (search the text on google to

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

On 20 April 2018 at 11:47, Uwe Geuder wrote: > But can you share state between distros? Isn't the purpose of distros to > use different options (variable settings) so the state would always be > different? If the input to the recipe is different then the hashes would be

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

On Fri, Apr 20, 2018 at 8:59 AM, Iván Castell wrote: > > Hello forum. > > We are trying to use yocto in a continuous integration environment with > different (production vs debug) scenarios. > > To setup a given scenario (production vs debug) we are using something like

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

Following up on my own message... On Fri, Apr 20, 2018 at 1:47 PM, Uwe Geuder wrote: > On Fri, Apr 20, 2018 at 10:59 AM, Iván Castell > wrote: > [...] >> However, things are getting complicated, because there is no way to >> exclude some recipes easily. For example,

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

Hi, had a similar question recently (search How did you separate release and development builds?) We have the split like this for now The release build would be something like: - has all the functions for production - attack surface is limited (no ssh, only the required apps) - config files set

Re: [yocto] Usage of yocto on different (production vs debug) scenarios

Hi! On Fri, Apr 20, 2018 at 10:59 AM, Iván Castell wrote: > We are trying to use yocto in a continuous integration environment with > different (production vs debug) scenarios. > > To setup a given scenario (production vs debug) we are using something like > this: >

[yocto] Usage of yocto on different (production vs debug) scenarios

Hello forum. We are trying to use yocto in a continuous integration environment with different (production vs debug) scenarios. To setup a given scenario (production vs debug) we are using something like this: $ SCENARIO=debug $ MACHINE= DISTRO=-${SCENARIO} source