[yocto] Necessary changes between SDK and eSDK builds

Hi I’m using yocto thud 2.6.1 and always build & provide sdk’s to our customers without problem. Now a customer requested an eSDK instead. According to the manual ( https://www.yoctoproject.org/docs/2.6/sdk-manual/sdk-manual.html#sdk-building-an-sdk-installer

[yocto] Necessary changes between SDK and eSDK builds

Hi I'm using yocto thud 2.6.1 always build & provide sdk's to our customers without problem. Now a customer requested an eSDK instead. According to the manual (https://www.yoctoproject.org/docs/2.1/sdk-manual/sdk-manual.html#sdk-building-an-sdk-installer), this should work identically by simpl

Re: [yocto] How to enforce installation of image specific config file/package

Hi Raj > > > > On Apr 1, 2016, at 5:38 AM, Isak Lichtenstein > > > wrote: > > > > Hi Joël, > >> > >> Hi, > >> > >> One idea may be to create one recipe per configuration file. > >> So in each image recipe, you would

Re: [yocto] How to enforce installation of image specific config file/package

Message d'origine- > > De : yocto-boun...@yoctoproject.org [mailto:yocto- > > boun...@yoctoproject.org] De la part de Isak Lichtenstein Envoyé : > > vendredi 1 avril 2016 11:35 À : yocto@yoctoproject.org Objet : [yocto] > > How to enforce installation of image

[yocto] How to enforce installation of image specific config file/package

Hi, I've got a package "A" that has a runtime dependency to a configuration file. This configuration file is image specific. For each image I've got a specific configuration package "config-image-X" that installs this needed configuration file and I build multiple image in the same build direct

[yocto] Changing default SDK path

Hi I'm building an SDK and decided to adapt the default SDK path for each release to allow users to have the SDK of multiple releases installed in parallel without them changing the path during installation. According to the Yocto Reference Manual, this can be achieved via the SDKPATH variable

Re: [yocto] Added package to RDEPENDS in packagegroup, image that IMAGE_INSTALLs packagegroup not rebuilt

Hi Martin, > -Ursprüngliche Nachricht- > Von: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] > Im Auftrag von Vuille, Martin (Martin) > Gesendet: 05 November 2014 17:39 > An: Paul Eggleton > Cc: yocto@yoctoproject.org > Betreff: Re: [yocto] Added package to RDEPEND

Re: [yocto] How to get fw_env.config installed

> > > >> I'm working on including the u-boot fw utility tools in my image, > >> specifically fw_printenv and fw_setenv. > >> For these to work the file fw_env.config needs to be placed at > /etc/fw_env.config. > >> > >> I can see in oe-core/meta/recipes-bsp/u-boot/u-boot.inc there is a > >> test th

Re: [yocto] How to get fw_env.config installed

Hi Matt, > I'm working on including the u-boot fw utility tools in my image, specifically > fw_printenv and fw_setenv. > For these to work the file fw_env.config needs to be placed at > /etc/fw_env.config. > > I can see in oe-core/meta/recipes-bsp/u-boot/u-boot.inc there is a test that > if >

Re: [yocto] Bash parser

Hi Olof, Thank you very much for your prompt answer > > On 14-07-16 11:36 +0200, Isak Lichtenstein wrote: > > In this method I'm using the bash syntax. But a lot of time the parser > > doesn't manage to parse my file properly. Examples: > > > > T

[yocto] Bash parser

an error while executing them. Example: TMP="file1, file2" tmp=${TMP//,/ } generates Bad substitution | WARNING: exit code 2 from a shell command. Does a page exist somewhere describing the bash features supported by the parser and also the executio

Re: [yocto] Create own image type

y useful. Managed to generate my image by using the "rpi-sdimg" recipe as base. BR Isak > > Lukas > > On 25 Jun 2014, at 16:04, Isak Lichtenstein > wrote: > > > Hi all, > > > > I'm trying to create my own image type. I thought that it wou

Re: [yocto] Create own image type

; BR, > Maxim. >>On Wed, Jun 25, 2014 at 5:04 PM, Isak Lichtenstein >> wrote: >>Hi all, >>  >>I’m trying to create my own image type. I thought that it would be enough to >>create a myImage.bbclass file implementing IMAGE_CMD_myImage and extending >

[yocto] Create own image type

Hi all, I'm trying to create my own image type. I thought that it would be enough to create a myImage.bbclass file implementing IMAGE_CMD_myImage and extending IMAGE_TYPES += " myImage". But this isn't working and I didn't find anything in the manual. It this possible at all ( can't imagine th

[yocto] Remove major version number from package name

ibdsp-test - 0.1-r26 - libdsp version 0.1-r26 Board support library for the libdsp0 - 0.1-r26 - libdsp version 0.1-r26 Board support library for the What can I add to my recipe to suppress the automatic addition of the major version number to the package name? Kind regards Isak Lichten