> I don't know anybody who redistributes source code as a single C file SQLite pioneered this approach, called an Amalgamation. It offers some noticeable adva

> I don't know anybody who redistributes source code as a single C file SQLite pioneered this approach, called an Amalgamation. It offers some noticeable advantages: https://www.sqlite.org/amalgamation.html https://www.sqlite.org/amalgamation.html It is gaining some followers: https://github.com/vinniefalco/Amalgamate https://github.com/vinniefalco/Amalgamate http://stackoverflow.com/questions/2719311/tool-to-create-an-amalgamation-combine-all-source-files-of-a-library-into-one-fo http://stackoverflow.com/questions/2719311/tool-to-create-an... http://lua-users.org/lists/lua-l/2008-08/msg00594.html 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.