From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 769] Update configuration menu for MIPS target
Date: Mon, 14 Dec 2009 05:56:08 -0600 [thread overview]
Message-ID: <200912140556.10177.minimod@morethan.org> (raw)
In-Reply-To: <20091213184620.D1DD9777D7@busybox.osuosl.org>
On Sun December 13 2009, bugzilla at busybox.net wrote:
> https://bugs.busybox.net/show_bug.cgi?id=769
>
> --- Comment #1 from Mike Z <minimod@morethan.org> 2009-12-13 18:46:19 UTC ---
> Screenshot of new MIPS target configuration sub-menu here:
> http://morethan.org/bldrt/xconfig2.png
>
Well, in spite of all the feedback I am getting on this project,
I think it looks good. It also generates the required gcc
options for cores from 1984 to October 2009.
Supports three modes:
"Full automatic" - based on Core codenames
"Semi-automatic" - Core codename + Manual modification of feature sets.
"Full manual" - Baby, your on your own.
The real key to this project was the splitting of Config.in.arch
into per-target files (Config.in.mips, Config.in.arm, ...).
That leaves each target arch to be dealt with by the lead contributor
and/or target maintainer (12 people rather than 1) **without**
any cross-target symbol dependencies (which Config.in.arch is full of).
Each target configuration sub-menu is "wrapped" with:
menu "MyArch target configuration"
depends on MyArch
- - - -
endmenu
Giving the closest thing to a namespace that kbuild understands.
The output interfaces with the existing Buildroot using the existing
symbol names + plus target generated booleans to drive the CFLAGS
option list generation.
Makes it much, much easier to add/remove/mark broken targets by arch.
Note: GCC supports 46 targets, **NO** I am not going to write 45 more
of these things! Not even if someone paid me.
But getting the other current targets to continue working again is
almost trivial - I planned it that way.
Mike
next prev parent reply other threads:[~2009-12-14 11:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 22:38 [Buildroot] [Bug 769] New: Update configuration menu for MIPS target bugzilla at busybox.net
2009-12-04 1:06 ` Michael S. Zick
2009-12-04 18:50 ` Michael S. Zick
2009-12-04 21:13 ` [Buildroot] [Bug 769] Q? So why does big-endian MIPS (mips) default to 64bit cores? Michael S. Zick
2009-12-05 13:05 ` [Buildroot] [Bug 769] New: Update configuration menu for MIPS target Michael S. Zick
2009-12-08 16:28 ` Michael S. Zick
2009-12-13 18:46 ` [Buildroot] [Bug 769] " bugzilla at busybox.net
2009-12-14 11:56 ` Michael S. Zick [this message]
2010-02-21 22:33 ` bugzilla at busybox.net
2013-12-26 21:41 ` bugzilla at busybox.net
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=200912140556.10177.minimod@morethan.org \
--to=minimod@morethan.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