TIGCC's build scripts have at least two characteristics which make them, in their current state, less than satisfactory for packaging (and therefore, making releases on a regular basis...):
* they compile and install at the same time (a common practice with make, ant, mvn and other build systems is to separate those goals);* they install under /usr/local/tigcc, instead of a more standard prefix such as /usr/share/tigcc.
only mentioned TIGCC's build scripts (specifically, what's wrong with the current state of them).
Let's also mention that GCC4TI's Windows installer defaults to installing in "C:\Program Files[b]GCC4TI[/b]". Of course, users are free to install GCC4TI over TIGCC, just as they're free to install TIGCC over GCC4TI.
I know you can do better, more constructive posts than ./2
