From: aldot at uclibc.org <aldot@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: target
Date: Sun, 28 Jan 2007 09:35:12 -0800 (PST) [thread overview]
Message-ID: <20070128173512.B0099485C4@busybox.net> (raw)
Author: aldot
Date: 2007-01-28 09:35:11 -0800 (Sun, 28 Jan 2007)
New Revision: 17604
Log:
- make sure to add board specific targets before the final generation of the filesystems/tarballs.
Until now, we did created the fs and only after that built/installed grub et al
Modified:
trunk/buildroot/Makefile
trunk/buildroot/target/Makefile.in
Changeset:
Modified: trunk/buildroot/Makefile
===================================================================
--- trunk/buildroot/Makefile 2007-01-28 16:59:30 UTC (rev 17603)
+++ trunk/buildroot/Makefile 2007-01-28 17:35:11 UTC (rev 17604)
@@ -67,7 +67,6 @@
# in the .config file.
include toolchain/*/*.mk
include package/*/*.mk
-include target/*/*.mk
# target stuff is last so it can override anything else
include target/Makefile.in
Modified: trunk/buildroot/target/Makefile.in
===================================================================
--- trunk/buildroot/target/Makefile.in 2007-01-28 16:59:30 UTC (rev 17603)
+++ trunk/buildroot/target/Makefile.in 2007-01-28 17:35:11 UTC (rev 17604)
@@ -1,3 +1,4 @@
+# make sure to put everything that is board-specific before the tarroot targets
include target/generic/Makefile.in
include target/device/Makefile.in
include target/x86/Makefile.in
@@ -3,2 +4,4 @@
include target/arm/Makefile.in
include target/powerpc/Makefile.in
+# and finally build the filesystems/tarballs
+include target/*/*.mk
next reply other threads:[~2007-01-28 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 17:35 aldot at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-25 8:01 [Buildroot] svn commit: trunk/buildroot: target aldot at uclibc.org
2009-02-04 12:47 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=20070128173512.B0099485C4@busybox.net \
--to=aldot@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