All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Koehler, Yannick" <yannick.koehler@hpe.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: externalsrc + sstate why is not compatible?
Date: Wed, 6 Dec 2017 10:47:13 +0200	[thread overview]
Message-ID: <d7cac90e-b07c-fe83-945f-82725ceeda81@linux.intel.com> (raw)
In-Reply-To: <CS1PR8401MB0840E46EE333163758C5D9B3ED320@CS1PR8401MB0840.NAMPRD84.PROD.OUTLOOK.COM>

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, instead of 20 repos (1 per
> packages) and 1 more for yocto recipe which complicates things when
> you want to submit a change.

You don't have to have 20 repos. You can place the modules into a single
repo with subdirs.

> Yet, the externalsrc disable the setscene tasks and set the
> BB_DONTCACHE variable.  I altered the script to remove those but then
> a change to the externalsrc folder is not detected. I wonder if it is
> because the S variable is set past the sstate algorithm and is then
> unable to consider the externalsrc folder as the real source
> location.  Any expert on this matter that can guide me to either make
> sstate works for external src or teach me how to have code + recipe
> in a single git repo.  I am certainly not the only case using such a
> pattern.

The bitbake documentation claims you can specify a directory in the 
file: fetcher, and then all of it will be unpacked to workdir. I've 
never seen or tried it myself, but maybe you can investigate in that 
direction, and make it work if it doesn't.

Alex


  reply	other threads:[~2017-12-06  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  2:15 externalsrc + sstate why is not compatible? Koehler, Yannick
2017-12-06  8:47 ` Alexander Kanavin [this message]
2017-12-06 14:13   ` Koehler, Yannick
2017-12-06 14:47     ` Marcelo E. Magallon
2017-12-06 16:59       ` Koehler, Yannick
2017-12-06 18:45         ` Marcelo E. Magallon
2017-12-06 18:51           ` Koehler, Yannick
2017-12-06 17:27     ` Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d7cac90e-b07c-fe83-945f-82725ceeda81@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=yannick.koehler@hpe.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.