Do you really think this makes sense? Much of the tools suite can be used with no toolchain at all, so I think having it as a standalone package is much more useful. In addition, it would make it easier to use the same tools with TIGCC and with GCC4TI and prevent a completely useless duplication of efforts.

Also note that TIGCC/*nix used to bundle the tools suite and I dropped that in 0.96 Beta 7 r1. What you're doing is a step backwards.

As for the few tools which are being bundled with TIGCC to support pucrunch compression, those are in principle no longer necessary because ld-tigcc now supports pucrunch natively (in the standalone version, not in the link.dll yet):[ul][li]on *nix, we currently bundle ttpack and ttbin2oth. Those will no longer be needed with KTIGCC 2. It would even be possible to backport the changes for using ld-tigcc's native pucrunch compression to KTIGCC 1.[/li][li]on W32, we currently bundle only ttpack. The functionality of ttbin2oth is implemented in the Delphi code. We would need some adjustments to the link.dll interface to be able to use the pucrunch from ld-tigcc, or we could drop link.dll altogether. In TIGCC, the plan is to get rid of link.dll by moving to KTIGCC 3.[/li][/ul]So I don't see the benefit in bundling the tools suite with the toolchain.