From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Uboot build system question
Date: Thu, 5 Jan 2012 18:10:42 -0500 [thread overview]
Message-ID: <201201051810.44195.vapier@gentoo.org> (raw)
In-Reply-To: <CADgt07nuuaQMNiu9OwacASYP_2ekf6BgE9ZibKdrZ5+sCOmO-w@mail.gmail.com>
On Wednesday 21 December 2011 06:21:21 Bharath H S wrote:
> I had a question regarding uboot build system.
> One starts a build for platform1 and without cleaning tree builds for
> platform2, what is the expected result?
> make <platform1>_config
> make <platform2>_config
>
> Is the final product build of platform2 or goes to inconsistent state
> or implementation dependent?
`make foo_config && make foo` should always output the same result regardless
of the initial state. if it isn't, post a patch to fix it.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120105/d56b5132/attachment.pgp>
prev parent reply other threads:[~2012-01-05 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:21 [U-Boot] Uboot build system question Bharath H S
2012-01-05 23:10 ` Mike Frysinger [this message]
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=201201051810.44195.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.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