From: Jan Weitzel <J.Weitzel@phytec.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] MLO
Date: Tue, 21 Feb 2012 16:25:59 +0100 [thread overview]
Message-ID: <1329837960.7354.9.camel@lws-weitzel> (raw)
In-Reply-To: <20120221150907.GG29102@pengutronix.de>
Am Dienstag, den 21.02.2012, 16:09 +0100 schrieb Michael Olbrich:
> Hi,
>
> On Tue, Feb 21, 2012 at 02:54:57PM +0100, Jan Weitzel wrote:
> > I am looking for a way to build a MLO (xloader) from barebox sources.
> > How can I reuse the barebox sources? I tried to play with
> > BAREBOX_BUILD_OOT, but didn't got a -build dir.
>
> You can only use *_OOT this is implemented in ptxdist for the used
> conf_tool. This only works for autoconf, qmake and cmake right now.
>
> You'd create separate rules for the MLO, right? Just reuse the same url,
> source etc. as barebox but use a different <PKG>_DIR. PTXdist will then
> extract the same patches into a different directory.
> This works much better reusing the same source in multiple packages.
Ok, is there a way to reuse BAREBOX_SOURCE
rules/barebox_mlo.make:
BAREBOX_MLO_SOURCE := $(BAREBOX_SOURCE)
didn't work.
Jan
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-02-21 15:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 13:54 Jan Weitzel
2012-02-21 15:09 ` Michael Olbrich
2012-02-21 15:25 ` Jan Weitzel [this message]
2012-02-21 16:47 ` Michael Olbrich
2012-02-23 7:31 ` [ptxdist] [RFC] Build MLO from barebox sources Jan Weitzel
2012-02-23 7:47 ` Jan Weitzel
2012-02-23 9:40 ` Michael Olbrich
2012-02-23 16:46 ` Jan Weitzel
2012-02-23 9:54 ` Michael Olbrich
2012-02-23 16:40 ` [ptxdist] [PATCH] " Jan Weitzel
2012-03-08 13:23 ` Michael Olbrich
2012-03-09 10:02 ` Jan Weitzel
2012-03-09 10:03 ` [ptxdist] [PATCH] barebox_mlo: fix resolving BAREBOX_MLO_ Jan Weitzel
2012-03-09 12:47 ` [ptxdist] [PATCH] Build MLO from barebox sources Michael Olbrich
2012-03-09 14:23 ` Jan Weitzel
2012-03-09 14:40 ` Michael Olbrich
2012-03-14 13:15 ` Jan Weitzel
2012-03-14 14:31 ` Michael Olbrich
2012-03-15 8:27 ` Jan Weitzel
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=1329837960.7354.9.camel@lws-weitzel \
--to=j.weitzel@phytec.de \
--cc=ptxdist@pengutronix.de \
/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