MA: Thanks. The patches look good, and I've merged them to the "next" branch of the git repository.
MB: Help is certainly welcome. Wiki pages with updated instructions, especially how to build (especially on windows) would address the biggest problems; perhaps, having recently succeeded, you could document what you did? As we're moving back to putting everything under mspgcc, and we have to keep mspgcc4 somewhat stable due to external references to its content by the WASP project, I'd suggest that be done on the existing mspgcc wiki at: https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=MSPGCC_Wiki If you need somebody to give you write access, contact me directly with your sourceforge userid. Just mark the stuff that's currently only relevant to mspgcc4; I don't think we're going to change the existing mspgcc infrastructure, just supersede it. I'm hoping for a new release under the mspgcc project within a couple weeks, with my updates that eliminate all the specialized hard-coded chip-specific addresses and assumptions. Unfortunately, "real work" has started to interfere again, so it's already later than I'd intended. We could also use a downstream packager for OSX, so people won't have to fight with the build process. (Ubuntu and Windows, too; I think Rob Spanton's doing Fedora/RedHat, though we haven't coordinated the release processes yet: that should be done with the return to mspgcc.) Peter On Fri, Sep 3, 2010 at 10:45 AM, Mark J. Blair <n...@nf6x.net> wrote: > > On Sep 3, 2010, at 7:33 AM, M. Andree wrote: > > Sorry for that, I've done that quick hack as an assistance to newbies, > but > > evidently it backfires on recent Cygwin and some Solaris versions. > > > > I have now figured that finding curses.h reliably and portably is a major > > undertaking (way more time that I can spend), and will anyways not > necessarily > > match what ./configure digs out later, so let's just remove the check. > > Don't feel too bad... making any complex package build portably can be very > difficult! > > I'm up and running with MSPGCC4 and mspdebug under OSX now, and I'm really > happy that this fully open and complete toolchain exists. I hope that I'll > be able to contribute in some small way towards its growth and improvement, > because I believe that it's beneficial for development tools to be free in > order to enable and stimulate creation of new and better things. > > -- > Mark J. Blair, NF6X <n...@nf6x.net> > Web page: http://www.nf6x.net/ > GnuPG public key available from my web page. > > > > > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users >
