John Tytgat wrote:
With GCCSDK GCC 4.1.1 Release 2 now being out of the door, I would like
to propose some development ideas and would appreciate some feedback.
For all clearness, this is what I can see myself doing for the coming
months/year(s ?) but not a promise it will actually be done. If other
people want to help out, of course feel free to join ;-)
[snippy]
My own goals are largely disjoint from this. However, I will be
applying what ever John is doing to other stuff, which is increasingly
automated. Perhaps the only are he's named where I would have
major input is any UnixLib rearrangement, should that be decided
to be a good idea.
Apart from that:
On going maintenance of autobuilder stuff. There's still a number of
items that don't build, and I've named items here several times that
certainly need work. One of the most external facing should be
getting people to contribute bugs and feature suggestions.
RiscPkg. Lots of work still needed here, and probably it will come
to the point where I need to do work on either or both of the backend
or frontend (or Alan's FE, etc). There's still much to be done
to make things consistent on riscos.info.
Shared library deployment. We've bitten the bullet with the GCC
release, so we'll see how that plays out. GCC is now the first
distributed application to make use of them. This makes for
example a Shared Firefox (needed for security features) more
practical, although that still needs a boat load of other
shared libraries to go along with it.
Wiki/documentation. Always stuff that can be done here; I think
the wiki stuff is perhaps too verbose, and could be broken up
some, although this kind of situation is typical of wiki
additions.
I think that's it for now.
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
