All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	 Brian Karcz <briank@russound.com>
Cc: yocto@yoctoproject.org
Subject: Re: creating images which include actively developed applications
Date: Fri, 01 May 2015 16:25:38 -0400	[thread overview]
Message-ID: <5543E142.2020707@gmail.com> (raw)
In-Reply-To: <1674505.cjWkHk81xC@peggleto-mobl.ger.corp.intel.com>

On 04/22/15 13:58, Paul Eggleton wrote:
> Hi Brian,
>
> On Wednesday 22 April 2015 15:32:06 Brian Karcz wrote:
>> Is there a way to create a recipe to build actively developed code located
>> in an external source directory? Basically skip the fetch and unpack steps
>> and always execute the compile and populate steps each time and image is
>> built?
> Indeed there is:
>
> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#building-software-from-an-external-source
>

Paul, I'm surprised you suggested externalsrc instead of just mentioning
devtool right from the start (doubly-surprised since you're the person
who wrote devtool!). Using devtool the "administration" (of creating a
recipe, etc) is done for you, no?

http://twoerner.blogspot.ca/2015/01/the-yocto-project-introducing-devtool.html


  parent reply	other threads:[~2015-05-01 20:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 15:32 creating images which include actively developed applications Brian Karcz
2015-04-22 17:58 ` Paul Eggleton
2015-04-22 20:51   ` Brian Karcz
2015-04-22 23:22     ` Paul Eggleton
2015-04-23  6:49       ` Khem Raj
2015-04-23  8:45         ` Paul Eggleton
2015-04-23  9:05           ` Khem Raj
2015-04-23  9:26             ` Paul Eggleton
2015-04-23  5:34   ` Mike Looijmans
2015-05-01 20:25   ` Trevor Woerner [this message]
2015-05-05  8:32     ` Paul Eggleton
2015-05-06  1:35       ` Michael_E_Brown
2015-05-06  2:02         ` Khem Raj

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=5543E142.2020707@gmail.com \
    --to=twoerner@gmail.com \
    --cc=briank@russound.com \
    --cc=paul.eggleton@linux.intel.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.