Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <trevor.woerner@linaro.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH 0/7] Developer workflow improvements
Date: Mon, 01 Dec 2014 23:54:03 -0500	[thread overview]
Message-ID: <547D45EB.6060508@linaro.org> (raw)
In-Reply-To: <cover.1416934753.git.paul.eggleton@linux.intel.com>


On 11/25/14 12:28, Paul Eggleton wrote:
> I've then added a new recipe auto-creation script, recipetool, which can
> take a source tree or URL and create a skeleton recipe to build it. 
...
>  * "recipetool create" ideally needs to become smarter and fill in
>    more details of the recipe. At some point we'll probably have to
>    make the process interactive and possibly have it automate parts of
>    the build process and examine the output; some things just can't be
>    practically detected from the source tree without building.

There is a tool "autoscan" which might be of some use here. If nothing
else, the resulting configure.scan file could be parsed for DEPENDS
information and perhaps PACKAGECONFIG items too.


  parent reply	other threads:[~2014-12-02  4:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 17:28 [RFC PATCH 0/7] Developer workflow improvements Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 1/7] lib/oe/patch: fall back to patch if git apply fails Paul Eggleton
2014-11-25 17:40   ` Paul Barker
2014-11-25 17:58     ` Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 2/7] lib/oe/patch: auto-commit when falling back from git am Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 3/7] lib/oe/patch: use --keep-cr with " Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 4/7] scripts/recipetool: Add a recipe auto-creation script Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 5/7] lib/oe: add recipeutils module Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 6/7] scripts/devtool: add development helper tool Paul Eggleton
2014-11-25 17:28 ` [RFC PATCH 7/7] scripts/devtool: Support deploy/undeploy function Paul Eggleton
2014-11-25 17:51 ` [RFC PATCH 0/7] Developer workflow improvements Paul Barker
2014-11-25 18:34   ` Paul Eggleton
2014-11-25 19:56 ` Trevor Woerner
2014-11-26  9:02   ` Paul Eggleton
2014-11-28 17:28 ` Trevor Woerner
2014-12-01 10:11   ` Paul Eggleton
2014-12-02  4:36     ` Trevor Woerner
2014-12-02 11:46       ` Paul Eggleton
2014-12-04 14:03         ` Trevor Woerner
2014-12-04 15:33           ` Paul Eggleton
2014-12-02  4:54 ` Trevor Woerner [this message]
2014-12-02 14:01   ` Paul Eggleton
2014-12-09 15:47     ` Trevor Woerner
2014-12-11 23:10       ` Trevor Woerner
2014-12-12 12:39         ` Paul Eggleton
     [not found] ` <54866CD7.1050102@linaro.org>
     [not found]   ` <7839390.odV1UMkpj8@peggleto-mobl5.ger.corp.intel.com>
2014-12-09 15:00     ` Trevor Woerner
2014-12-09 15:10       ` Paul Eggleton
2014-12-09 15:39         ` Trevor Woerner
2014-12-09 16:08           ` Paul Eggleton
2014-12-09 18:58             ` Trevor Woerner
2014-12-10 17:51               ` Paul Eggleton
2014-12-11 17:14                 ` Paul Eggleton
2014-12-11 18:30                   ` Trevor Woerner
2014-12-11 18:55                     ` Paul Eggleton
2014-12-11 19:16                       ` Trevor Woerner
2014-12-11 19:43                         ` Trevor Woerner
2014-12-11 21:35                           ` Paul Eggleton
2014-12-11 23:14                             ` Trevor Woerner
2014-12-12 13:01                             ` Otavio Salvador
2014-12-14  3:47                   ` Trevor Woerner

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=547D45EB.6060508@linaro.org \
    --to=trevor.woerner@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox