Re: [yocto] externalsrc + sstate why is not compatible?

On Wed, Dec 06, 2017 at 10:59:37AM -0600, Koehler, Yannick wrote: > Ok, will try that. If that works, I may see if I can alter the file > fetcher to use symlinks, not sure if sstate subsystem will like that > or not. That was my idea, but I've never tried it. I'm sure the devil is in the details.

Re: [yocto] externalsrc + sstate why is not compatible?

, which we also uses. -- Yannick Koehler -Message d'origine- De : Magallon, Marcelo Envoyé : 6 décembre 2017 13:46 À : Koehler, Yannick Cc : Alexander Kanavin ; yocto@yoctoproject.org Objet : Re: [yocto] externalsrc + sstate why is not compatible? On Wed, Dec 06, 2017 at 10:59:37AM

Re: [yocto] externalsrc + sstate why is not compatible?

On 12/06/2017 04:13 PM, Koehler, Yannick wrote: When you say "subdirs", are you referring to submodules or something along those line? We have used attempted to use submodules and it still required 20 + 1 repo and the overhead is similar to yocto + 20 repo but then you have yocto + 20 repos +

Re: [yocto] externalsrc + sstate why is not compatible?

? -- Yannick Koehler -Message d'origine- De : Magallon, Marcelo Envoyé : 6 décembre 2017 09:47 À : Koehler, Yannick Cc : Alexander Kanavin ; yocto@yoctoproject.org Objet : Re: [yocto] externalsrc + sstate why is not compatible? On Wed, Dec 06, 2017 at 02:13:26PM +, Koehler, Yannick

Re: [yocto] externalsrc + sstate why is not compatible?

On Wed, Dec 06, 2017 at 02:13:26PM +, Koehler, Yannick wrote: > In regards to file fetcher, I will go check the code, I thought the > unpack would only occurs for tarball, not subdir. If you have: SRC_URI := "file://some-dir/" and your tree looks somewhat like this: .git

Re: [yocto] externalsrc + sstate why is not compatible?

oehler, Yannick ; yocto@yoctoproject.org Objet : Re: [yocto] externalsrc + sstate why is not compatible? On 12/06/2017 04:15 AM, Koehler, Yannick wrote: > In our situation, we have many packages that are in-house, as such we > use a local folder for the several in-house modules. To do

Re: [yocto] externalsrc + sstate why is not compatible?

On 12/06/2017 04:15 AM, Koehler, Yannick wrote: In our situation, we have many packages that are in-house, as such we use a local folder for the several in-house modules. To do so, we need to use externalsrc to point to the local code so that the git repo contains both the code + recipe, instea

[yocto] externalsrc + sstate why is not compatible?

In our situation, we have many packages that are in-house, as such we use a local folder for the several in-house modules. To do so, we need to use externalsrc to point to the local code so that the git repo contains both the code + recipe, instead of 20 repos (1 per packages) and 1 more for yo

[yocto] externalsrc: enable sstate for git srctrees based on makefile

Hi Yocto, I am already aware of sstate never works for externalsrc recipes. My environment is using externalsrc in recipes for makefile based sources in git. I am aware that the source is not going to change and only builds one time in my production build. I want to use sstate if nothing has

[yocto] externalsrc: enable sstate for git srctrees based on makefile

Hi Yocto, I am already aware of sstate never works for externalsrc recipes. My environment is using externalsrc in recipes for makefile based sources in git. I am aware that the source is not going to change and only builds one time in my production build. I want to use sstate if nothing has

[yocto] externalsrc sstate

Dear Yocto, While using externalsrc for the recipes, sstate is not working for the recipes. Is it possible to enable setscene tasks, if srctree_hash_files reports nothing has changed? my environment is using makefile based sources in git. Can you please provide your feedback? Or do i need to co

Re: [yocto] EXTERNALSRC

Ah - thank you! It's very clear now. Yes I think the formatting will make it more clear. Examples also help :) Something's still not working the way I'm expecting, though. According to this : "...this cla

Re: [yocto] EXTERNALSRC

On Wed, Sep 10, 2014 at 7:07 AM, Rifenbark, Scott M wrote: > I should have used a formatting tag in the manual source to indicate > "myrecipe" as user input. Without the formatting, it implies that "myrecipe" > is literal when it is not. I guess the example is not technically wrong if > the r

Re: [yocto] EXTERNALSRC

I like your added information about setting it in the recipe. I will add that as well. Scott >-Original Message- >From: Nicolas Dechesne [mailto:nicolas.deche...@linaro.org] >Sent: Tuesday, September 09, 2014 10:02 PM >To: Rifenbark, Scott M >Cc: Nemicolopterus Crypticus

Re: [yocto] EXTERNALSRC

On Wed, Sep 10, 2014 at 6:51 AM, Rifenbark, Scott M wrote: > This is an error in the manual. I have been formatting the user-supplied > portions of examples now in an italisized font. This one needs to be fixed. hmm. i don't seem to see what's wrong in the user manual.. also, the _pn-banana i

Re: [yocto] EXTERNALSRC

Behalf Of Nicolas Dechesne >Sent: Tuesday, September 09, 2014 8:53 PM >To: Nemicolopterus Crypticus >Cc: yocto@yoctoproject.org >Subject: Re: [yocto] EXTERNALSRC > >On Tue, Sep 9, 2014 at 11:51 PM, Nemicolopterus Crypticus > wrote: >> What else do I need to do in order t

Re: [yocto] EXTERNALSRC

On Tue, Sep 9, 2014 at 11:51 PM, Nemicolopterus Crypticus wrote: > What else do I need to do in order to correctly set the source directory? > The dev manual recommends this: > > EXTERNALSRC_pn-myrecipe = "/some/path/to/your/source/tree" > > > How literal is "pn-myrecipe"? If I have a recipe calle

[yocto] EXTERNALSRC

Following this: http://www.yoctoproject.org/docs/1.6.1/dev-manual/dev-manual.html#building-software-from-an-external-source I've got this in my local.conf file: INHERIT += "externalsrc" EXTERNALSRC_src1 = "${TOPDIR}/../" EXTERNALSRC_BUILD_src1 = "${WORKDIR}/${BPN}/{PV}/" EXTERNALSRC_src2 = "