In case anyone is wondering: The actual platform was Chumby [1], and Python ran great on it. We had a little twisted [2] application that displayed images and played sound. To display the images we just wrote an image file (after using PIL to manipulate it) to /dev/fb. It was really fun! I just double checked the hardware the chumby: A 350 MHZ ARM9 processor with 64 megabytes of SDRAM. It sounds a little crazy to me now to think of transforming images using PIL in 64 megabytes of ram, but it actually worked quite well.
[0] http://www.scratchbox.org/
I tried pulling the files out of nimcache/*.c, but it is wanting to include nimbase.h.
Is there a way to compile an entire Nim program to a single self-contained .c file (ie. an amalgamation, aka SQLite?)
SQLite pioneered this approach, called an Amalgamation. It offers some noticeable advantages:
https://www.sqlite.org/amalgamation.html
It is gaining some followers:
https://github.com/vinniefalco/Amalgamate
http://stackoverflow.com/questions/2719311/tool-to-create-an...
http://lua-users.org/lists/lua-l/2008-08/msg00594.html
> Usually people redistributing source code don't mind having several files bound together by some make|build script.
A single .c file is easier to integrate into various build systems. For example a Visual Studio project, or another Makefile without needing a separate script. It's just cleaner.
> Most people willing to get something redistributable prefer a binary static|dynamic library or final executable.
These aren't portable like a C source file is.
Go is garbage collected and has an opinionated ABI and runtime. Completely different beasts.
Someone has revived the LLVM C Backend. Hopefully this could be a path to Rust->C compilation: https://github.com/draperlaboratory/llvm-cbe
Compiling to C is so important to me that I may check out Nim as an alternative to Rust, despite liking Rust very much.