The combination (TIGCC IDE|KTIGCC) + TPR has several well-known drawbacks. (At least) the following shortcomings of (TIGCC IDE|KTIGCC) + TPR should be addressed:
[ul][li]behaviour with relative paths...[/li]
[li]the '1 project = 1 compilation of a given program' mantra is horrendous when there are MANY programs (ExtGraph: 33 demos + 1 other test program, this number will increase);[/li]
[li]TPRs don't make it simple to compile subsets of the program with different compilation options (TI-Chess). I mean, multiple TPRs that make function archives and link everything together is rubbish
[/li]
[li]TPRs are not designed for multiple compilations, e.g:
[ul][li]on-calc-incompatible programs (mostly all TICT programs);[/li]
[li]multiple language localizations (TI-Chess, TICT-Explorer).[/li][/ul]
[li]Handle 'verbose' mode of tprbuilder and the tools it calls. The current KTIGCC doesn't understand verbose mode and thinks many things went wrong...[/li][/ul]