From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/u-boot
Date: Tue, 06 Jan 2009 13:59:39 +0100 [thread overview]
Message-ID: <87iqossi84.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1231246236.32308.68.camel@elrond.atmel.com> (Ulf Samuelsson's message of "Tue\, 06 Jan 2009 13\:50\:36 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Ulf> m?n 2009-01-05 klockan 21:12 +0100 skrev Peter Korsgaard:
>> >>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>>
>> Hi,
>>
Ulf> The "complex" file name is needed, unless you only
Ulf> work with a single board.
>>
>> I don't get it - Isn't that why we have binaries/<project>?
Ulf> YOu copy things to binaries/PROJECT to have a single directory
Ulf> which you can compress, but if you copy the stuff to
Ulf> the tftp directory then you have a mess.
Ulf> You have to manually rename this.
tftp directory? Is that this ATMEL_COPY_TO thing? I don't recall that
ever being discussed on the list.
Lets just start by making things simple before adding all kinds of
extra stuff. Buildroot should imho just worry about building stuff and
putting it under binaries/<project>, and not install it somewhere for
tftp/nfs/whatever.
>> Even so,
>> isn't that the same problem with the other files? (file system images,
>> kernels)?
Ulf> The kernel is already doing this in the "advanced" makefile.
Ulf> The rootfs should be doing it. and in this case PROJECT Is definitely
Ulf> the right one to use.
Ulf> We obviously need to find a way that does not break the build of
Ulf> course.
I don't agree. Having things under binaries/<project> is enough.
Ulf> Many targets define BR2_BOARD_NAME in their Config.in's
Ulf> and it may make sense to have a common BR2_BOARD_NAME
Ulf> Then it will be always be defined.
Ulf> Default to "uclibc" is probably OK.
>>
>> Isn't that what we have BR2_PROJECT for?
Ulf> Yes and no,
Ulf> You can use BR2_PROJECT, but if you:
Ulf> make XXXX_config
Ulf> when building u-boot-<VERSION>, it also makes sense to name the binary
Ulf> <XXXX>-u-boot-<VERSION>-<DATE>.bin
Ulf> because regardless of which project you are building,
Ulf> the binary should end up the same.
Ulf> <DATE> is there to give you some kind of revision information
Ulf> so you do not overwrite older working results.
Ulf> It is not perfect, but I think it is good enough.
Sorry, I still don't think this belongs in buildroot.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-06 12:59 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 16:12 [Buildroot] svn commit: trunk/buildroot/target/u-boot jacmet at uclibc.org
2009-01-05 18:12 ` Ulf Samuelsson
2009-01-05 18:16 ` Ulf Samuelsson
2009-01-05 20:14 ` Peter Korsgaard
2009-01-05 20:12 ` Peter Korsgaard
2009-01-06 12:50 ` Ulf Samuelsson
2009-01-06 12:59 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 15:19 jacmet at uclibc.org
2009-02-10 15:19 jacmet at uclibc.org
2009-02-10 15:19 jacmet at uclibc.org
2009-02-07 6:57 jacmet at uclibc.org
2009-02-04 23:15 jacmet at uclibc.org
2009-01-26 14:49 jacmet at uclibc.org
2009-01-26 14:49 jacmet at uclibc.org
2009-01-26 14:04 jacmet at uclibc.org
2009-01-26 11:46 ulf at uclibc.org
2009-01-22 18:46 ulf at uclibc.org
2009-01-22 10:15 jacmet at uclibc.org
2009-01-21 15:49 jacmet at uclibc.org
2009-01-20 8:11 ulf at uclibc.org
2009-01-11 21:39 ulf at uclibc.org
2009-01-24 8:21 ` Peter Korsgaard
2009-01-24 10:55 ` Ulf Samuelsson
2009-01-24 11:43 ` Peter Korsgaard
2009-01-24 15:27 ` Dan Lyke
2009-01-08 14:58 jacmet at uclibc.org
2009-01-08 14:58 jacmet at uclibc.org
2009-01-06 14:16 ulf at uclibc.org
2009-01-06 14:26 ` Peter Korsgaard
2009-01-06 16:06 ` Ulf Samuelsson
2009-01-05 16:16 jacmet at uclibc.org
2009-01-05 15:52 jacmet at uclibc.org
2009-01-03 15:03 nkukard at uclibc.org
2009-01-03 0:02 ulf at uclibc.org
2009-01-03 20:46 ` Peter Korsgaard
2009-01-03 20:18 ` Ulf Samuelsson
2009-01-03 0:00 ulf at uclibc.org
2009-01-03 20:28 ` Peter Korsgaard
2009-01-03 20:37 ` Ulf Samuelsson
2008-08-20 20:04 jacmet at uclibc.org
2008-08-20 20:04 jacmet at uclibc.org
2008-08-20 20:04 jacmet at uclibc.org
2008-07-08 10:53 jacmet at uclibc.org
2008-07-04 22:18 ulf at uclibc.org
2008-07-07 13:27 ` Peter Korsgaard
2008-06-17 8:04 jacmet at uclibc.org
2008-06-13 13:46 jacmet at uclibc.org
2008-06-12 7:27 jacmet at uclibc.org
2008-06-11 13:07 jacmet at uclibc.org
2008-06-12 5:14 ` Hamish Moffatt
2008-06-12 7:28 ` Peter Korsgaard
2008-04-23 14:52 jacmet at uclibc.org
2008-04-23 14:59 ` Thiago A. Corrêa
2008-04-23 15:20 ` Peter Korsgaard
2008-04-23 16:22 ` Ulf Samuelsson
2008-04-23 17:35 ` Bernhard Fischer
2008-04-23 17:39 ` Ulf Samuelsson
2008-04-23 18:37 ` Bernhard Fischer
2008-04-23 18:29 ` Peter Korsgaard
2008-04-23 14:52 jacmet at uclibc.org
2008-04-23 13:03 jacmet at uclibc.org
2008-04-23 16:09 ` Ulf Samuelsson
2008-04-23 18:05 ` Peter Korsgaard
2008-04-23 18:35 ` Ulf Samuelsson
2008-04-23 13:03 jacmet at uclibc.org
2008-04-23 13:03 jacmet at uclibc.org
2008-04-23 10:30 jacmet at uclibc.org
2008-04-09 7:02 jacmet at uclibc.org
2008-04-09 7:02 jacmet at uclibc.org
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=87iqossi84.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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