Lionel Debroux (./6) :
libopcodes is a different beast indeed, but are the external bits of ld-tigcc and TIEmu extracted through automated means ? (for subsets of a given file, a sed script that keeps lines between by two markers would certainly do the job just fine)

No, it's completely forked. Where I merge changes (which so far I only did for the __attribute__((may_alias))-related stuff in the integer definitions, which by the way needs fixing again for GCC 4.3 - I don't remember merging any other change one way or the other, in fact I haven't touched dasm-tigcc for a while), I do it by hand.

The more the maintenance and building process is automated, the easier it is to make releases.

Well, that assumes I want to merge the changes in the first place. And that there are any changes to merge.

What about "TI-68k Developer Utilities" ? That would emphasize that these are "companion tools" to the main development tools that the rest of the TIGCC/GCC4TI toolchain is.

That sounds good.

For testing purposes, where can I get shrnklib-compressed executables ?

You need to call ttstrip, shrink92 and ttbin2oth.