[help]need compile environment for tinycore 2.x

[huy]

I found compiletc.tce/tcz for  tinycore 1.x ,but couldn't found it for  tinycore 2.x.
I installed tinycore 2.x instead of tinycore 1.x ,because it supported glibc_i18n_locale.
I wanted to compile Chinese Input.
Anyone help me? Thx

[Jason W]

gcc-binutils would be the compile extension for 2.x, plus whatever other development extensions may be required, which would depend on what is being built.  The info file lists helper apps that may be needed.

[softwaregurl]

gcc-binutils would be the compile extension for 2.x

eek, i would not have guessed.  maybe everything to do with compile has an app browser searchable word/phrase (compile for tc) with forum sticky and wiki docs.

[Juanito]

A few people had suggested that having everything wrapped together in compiletc (and prior to that compile-3.3.5.uci) might not be a good idea.

For this reason, I thought I'd try breaking up the compiletc extension in tc_2.x - maybe I should have thought of a smarter name than gcc-binutils, but this is an accurate description of what it contains 

One thing that you need to keep in mind is that if compiling an application requires a "compile helper app" like flex, bison, gettext, etc - sometimes the error message you get is very clear about what it is missing and sometimes there is almost no way to know what is missing except by experience. For this reason, I usually load all of the helper apps listed in the gcc-binutils info file...

[danielibarnes]

A few people had suggested that having everything wrapped together in compiletc (and prior to that compile-3.3.5.uci) might not be a good idea.

I agree. What we need is a compiletc extension that may not contain files but has a .dep which lists all of the extensions required for compilation. This has benefits:

• It is easy to find, especially for users of 1.x
• You can update components individually without rebuilding a huge extension
• New components can be added (new languages for example)
• The 1.x extension could be updated to use this method transparently

[^thehatsrule^]

I agree. What we need is a compiletc extension that may not contain files but has a .dep which lists all of the extensions required for compilation. [...]

already been planned