From: Mike Looijmans <mike.looijmans@topic.nl>
To: <yocto@yoctoproject.org>
Subject: Re: creating images which include actively developed applications
Date: Thu, 23 Apr 2015 07:34:56 +0200 [thread overview]
Message-ID: <55388480.2000304@topic.nl> (raw)
In-Reply-To: <1674505.cjWkHk81xC@peggleto-mobl.ger.corp.intel.com>
On 22-04-15 19: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
Man, I've been working with OE for years, and this is the first time I ever
saw this.
You should create a link to this page using ten feet neon tubes. Seriously.
People have been asking me this question over and over, and all I had to offer
was some crappy scripts to invalidate and rebuild a package.
Kind regards,
Mike.
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
next prev parent reply other threads:[~2015-04-23 9:17 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 [this message]
2015-05-01 20:25 ` Trevor Woerner
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=55388480.2000304@topic.nl \
--to=mike.looijmans@topic.nl \
--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.