Ecere Flavors (vanilla, tight, ecere, ecereCOM)

[redj]

Question from JF:
What is ecere-vanilla as opposed to 'regular' ecere?

-redj

[jerome]

ecere-vanilla is something meant to be very light and small, the minimum amount of stuff to get a GUI app running. It also limits the number of dependencies.
Among other things, it strips out all 3D graphics, extra graphic format support, true type fonts (freetype) support (on Windows at least, not on X I believe) and networking capabilities.

ecereCOM is the bare minimum to run eC code (No GUI toolkit / graphics)

tight is just a config I believe, optimizing for size as opposed to speed, and UPX compressed, but nothing stripped out.

ecere is the default.

[jerome]

Forgot to mention the Ecere Vanilla config was static, and UPX'ed, an Ecere GUI app can be as small as 320k, including Ecere itself (with no external shared library dependencies).

EAR allows you to produce self-extracting executables, and it uses Ecere Vanilla to produce the core of those self-extracting executables (extract, which can also be used as an Ecere Archive viewer / extraction tools).