Mono ("Jumbo") build

[absolutelynothinghere]

Some projects offer a mono or "jumbo" build option, where users can download one .c file and compile it into an executable directly. This single .c file is an amalgamation of all existing source files and headers, and is automatically generated every release.
Example projects: SQLite, wak, u-config.

If you're interested in offering a mono build option, I've created a basic amalgamation script along with a Makefile entry.

P.S. Consider adding include guards to make.h.

Makefile entry

pdpmake_mono.c:
	./amal.sh $(OBJS:.o=.c) > $@

amal.sh

#!/bin/sh
set -e

# display help
if [ ${#} -lt 1 ]; then
    echo "Usage: amal.sh FILE.c [FILE.c ...] > OUT.c"
    exit 1
fi

# log of files included so far to avoid double inclusion
LOG="`mktemp`"
true > "${LOG}"

# iterate over input files
while [ ${#} -gt 0 ]; do
    # input file location, to resolve relative include files
    HERE="$(dirname "$(readlink -f "${1}")")"
    # iterate over lines
    cat "${1}" | while IFS= read -r line; do
        # if normal line, pass it through
        if [ -z "`printf "%s\n" "${line}" | grep '^#.*include.*"'`" ]; then
            printf "%s\n" "${line}"
        # if include line, replace it if not already included
        else
            INC="${line%\"*}"
            INC="${INC#*\"}"
            if [ -n "`grep "${HERE}/${INC}" "${LOG}"`" ]; then continue; fi
            echo "${HERE}/${INC}" >> "${LOG}"
            cat "${HERE}/${INC}"
        fi
    done
shift; done

# cleanup
rm -f "${LOG}"

[rmyorston]

Oh yes, I know about amalgamations. In fact, one is involved behind the scenes in my development workflow for pdpmake:

• Actual development takes place in a private repository which is a superset of this one.
• When an update is to be made the relevant files are copied here.
• An amalgamation is created and tested in the private repo, which is then further munged so it can be included in upstream BusyBox. (This version isn't actually released because I still haven't got round to submitting it to BusyBox.)
• The BusyBox version is then ported to busybox-w32.

I hadn't considered there would be any general interest in having the ability to create an amalgamation. It doesn't seem particularly useful. But what do I know?

Would anyone else like to have this superpower?

[absolutelynothinghere]

I hadn't considered there would be any general interest in having the ability to create an amalgamation. It doesn't seem particularly useful.

Single-file source distribution in general has been getting popular for a while now. I guess pdpmake has no need for such a distribution method, but it would turn it from a program that's easy to compile into a program that's extremely easy to compile... The source files are already modular enough that when I tried concatenating them the compilation just worked (tested with 2.0.1).