From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Brad Litterell <brad@evidence.com>
Cc: yocto@yoctoproject.org, Chris Larson <clarson@kergoth.com>
Subject: Re: Bitbake on live (uncommitted) code
Date: Fri, 13 Sep 2013 10:55:44 +0100 [thread overview]
Message-ID: <22610256.9HCK7tef9Y@helios> (raw)
In-Reply-To: <CABcZAN=QM=Tj=vtsdXERZy=9gcs6vBr1cpw+4Fr9USHuthCxkQ@mail.gmail.com>
On Thursday 12 September 2013 17:23:53 Chris Larson wrote:
> On Thu, Sep 12, 2013 at 4:53 PM, Brad Litterell <brad@evidence.com> wrote:
> > I've grown to really appreciate bitbake for compiling code from a myriad
> > of sources, however, what is the recommended course for source I am
> > currently doing live development on? My code base lives in a couple of
> > git
> > repos that do NOT map one-to-one with recipes and I don't really want to
> > store the source mixed in with the recipe meta data anyway, nor do I want
> > to be forced to commit it to git just to do a build.
> >
> > Currently I run a pre-bitbake script that creates a tarball out of the
> >
> > source, but that is easy to forget and makes building a new image a two
> > step proces. Since it is a build step I'd like it to be done by bitbake.
> >
> > Is there a recommended way to go about this?
>
> See externalsrc.bbclass.
Also the manual section that talks about using it:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#building-software-from-an-external-source
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-09-13 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 23:53 Bitbake on live (uncommitted) code Brad Litterell
2013-09-13 0:23 ` Chris Larson
2013-09-13 9:55 ` Paul Eggleton [this message]
2013-09-13 10:04 ` Hans Beckérus
2013-09-13 10:51 ` Paul Eggleton
2013-09-17 17:48 ` Brad Litterell
2013-09-17 18:01 ` Paul Eggleton
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=22610256.9HCK7tef9Y@helios \
--to=paul.eggleton@linux.intel.com \
--cc=brad@evidence.com \
--cc=clarson@kergoth.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.