A visit to #43oh recently reminded me how many places people go to find
mspgcc-related information, and how out of date most of it is. I've started
to clean that up some, but it's a huge task, so I'm just taking the first
steps, and asking y'all to step in to help finish the job. I'm encouraging
this by trying to make most of the old stuff harder to get to.
I've updated the mspgcc4 project to mark it inactive and direct people back
to the mspgcc project. That part was simple.
Until there's a new manual in at least stub form, I've redirected the mspgcc
homepage to the
wiki<http://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=MSPGCC_Wiki>.
The old home page is still accessible from its original
URI<http://mspgcc.sourceforge.net/>(for now).
I've also replaced the wiki entry point with a new one with basic
information. There's a link to the old root page, and to everything else
from there, but since virtually all of it is out of date I haven't hooked it
into the new main page. I have added an "Installation" section with pages
for Windows and various Linux distributions, and would ask that downstream
packagers update that as appropriate, and add their names so they get credit
for providing this extremely valuable service.
(Note that I use a topic:subtopic naming convention for wiki pages.
Personal preference; I probably won't rearrange things if you add a useful
page with some other convention.)
The former mspgcc home page (generated with ht2html), and the manual
(generated with docbook) both include material that I personally don't feel
should be part of the "official" semi-static release-oriented mspgcc
documentation. This feeling comes from my preference to reduce the scope of
my responsibilities to the point where they're manageable, and to make
everything else "somebody else's problem". If you feel strongly enough
otherwise to want to make it *your* problem, speak up and we'll give it a
try.
For now, though, "how do I install this thing" will be on the wiki. The
hints I give in the README and the patch headers are as far as I'm going to
go. Most of "how do I use this thing" is better handled somewhere else
too. There's TI's documentation. There's hackaday.com/tag/msp430/.
There's http://www.43oh.com/. There's a section on the wiki people can fill
in.
I don't plan to do anything more with the wiki.
I will continue to update the binutils and gcc documentation to make sure
the necessary target-specific information is present and accurate, including
assembler directives, function and variable attributes, built-in functions,
compiler options, etc. This may take a while, and will be done in the
context of the 4.6.x-based mspgcc that I'm starting to work on now.
At some point, I may collect the still-relevant pieces from the old web site
and user documentation and combine them into a new manual. This would
include more verbose discussion and examples of things like watchdog
management and interrupt handling than is appropriate for the gcc
documentation, but would not include reference information on the MSP430
architecture or embedded programming in general. If I do this, it'll
probably be in reStructured text, maybe using Sphinx, so both web and
printable formats can come from the same source. If somebody else takes
over and does it first, it'll be in their choice of format.
If you want to take over the manual, let me know.
Peter
------------------------------------------------------------------------------
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
