All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Sundius <msundius@sundius.com>
To: openembedded-devel@openembedded.org
Subject: Re: Development and Open Embedded
Date: Wed, 6 May 2009 22:09:29 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090506T220347-812@post.gmane.org> (raw)
In-Reply-To: b6ebd0a50905061444r2d012f65t67fe8af4663a6ae5@mail.gmail.com

Chris Larson <clarson <at> kergoth.com> writes:


> > I'm wondering if anyone has done such a thing as creating a
> > recipe that forgoes the "fetch" task and point the ${S} to
> > a local devel tree.. then adds an extra onto the make command
> > to place the object in another directory (maybe ${O})...
> >

> I have a little class somewhere around here that did that.  Killed
> fetch/unpack/patch, set S to ${TOPDIR}, set O to
> ${TOPDIR}/obj-${HOST_SYS} or so, redirect WORKDIR to
> ${TOPDIR}/somethingorother, etc.  It works very well.  You can then
> add the recipe from the source tree to your BBFILES, or add your
> development area to COLLECTIONS or so, and it mostly just works.
> Cleaning up something like that would be a huge boon to the
> application and kernel developer use cases, which are sadly not well
> satisfied in current openembedded.


I'm happy to help clean it up try it out etc for kernel and other
stuff. We're told here by our boss that giving back is good, so I'm
happy to do it if you don't mind sharing the code and giving me a
head start.

mike





  reply	other threads:[~2009-05-06 22:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 21:33 Development and Open Embedded Michael Sundius
2009-05-06 21:44 ` Chris Larson
2009-05-06 22:09   ` Michael Sundius [this message]
2009-05-07  5:25 ` Roman I Khimov

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=loom.20090506T220347-812@post.gmane.org \
    --to=msundius@sundius.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.