From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: getting bitbake-1.8.12 for the org.openembedded.dev branch?
Date: Mon, 27 Jul 2009 10:44:39 +0200 [thread overview]
Message-ID: <200907271044.40262.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <200907270743.12287.holger+oe@freyther.de>
Dnia poniedziałek, 27 lipca 2009 o 07:43:12 Holger Hans Peter Freyther
napisał(a):
> Marcin, Koen. Do you switch from dev to stable? How do you do that?
> Do you have two complete build trees for stable/dev?
I have OE metadata in ~/devel/oe/openembedded/ and use it to any builds
which use .dev branch. I also use that directory for all pushing stuff
(for .dev, stable/2009 and others).
Builds are stored in ~/devel/build/NAME-OF-BUILD/ directory. They are
mostly from .dev tree.
To build from stable/2009 I have ~/devel/build/stable/ directory which
contains copy of OE metadata (without pushing).
For .dev builds I use Bitbake from ~/devel/bitbake/ which contains GIT
tree with master (1.9.x) branch selected.
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
next prev parent reply other threads:[~2009-07-27 8:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 12:15 getting bitbake-1.8.12 for the org.openembedded.dev branch? Robert P. J. Day
2009-07-25 12:52 ` Holger Hans Peter Freyther
2009-07-25 13:01 ` Robert P. J. Day
2009-07-25 13:42 ` Graeme Gregory
2009-07-25 14:11 ` Richard Purdie
2009-07-26 10:44 ` Robert P. J. Day
2009-07-25 14:51 ` Holger Hans Peter Freyther
2009-07-25 21:43 ` Robert P. J. Day
2009-07-26 9:05 ` Koen Kooi
2009-07-27 5:43 ` Holger Hans Peter Freyther
2009-07-27 8:44 ` Marcin Juszkiewicz [this message]
2009-07-27 11:33 ` Koen Kooi
2009-07-27 15:06 ` Robert P. J. Day
2009-07-25 19:55 ` Marcin Juszkiewicz
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=200907271044.40262.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--cc=openembedded-devel@lists.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.