apenwarr-redo/redoconf/rc_vars.od

. ./redoconf.rc

# this is called by each call to replaceln() and appendln().
RC_KEYS="RC_KEYS"
rc_hook() {
	contains_line "$RC_KEYS" "$1" || RC_KEYS="$RC_KEYS$NL$1"
}
rc_include _all.rc

# Escape double-quote and backslash so they can
# be included as a C-style double-quoted string.
cquote() {
	local v="$(xecho "$1" | sed -e 's,[\"\\],\\&,g' -e 's,$, \\,')"
	printf '"%s"' "${v% \\}"
}

(
	echo "# Automatically generated by rc_vars.od"
	for k in $(echo "$RC_KEYS" | sort); do
		[ "$k" != "RC_INCLUDES" ] || continue
		eval v=\$$k
		echo "$k=$(shquote "$v")"
	done
) >$3
redo-stamp <$3
Experimental new redoconf C/C++ build/autoconfiguration system. To test it out, try this: ./do -j10 build cd docs/cookbook/c redo -j10 test It should detect all the compilers on your system and make three separate builds for each one: normal, debug, and optimized. Then it tries to run a test program under each one. If there are windows cross compilers and you also have 'wine' installed, it'll try running the test program under wine as well. redoconf currently has no documentation other than the example program. We'll fix that later. 2019-02-03 01:14:51 -05:00			`. ./redoconf.rc`

			`# this is called by each call to replaceln() and appendln().`
			`RC_KEYS="RC_KEYS"`
			`rc_hook() {`
			`contains_line "$RC_KEYS" "$1" \|\| RC_KEYS="$RC_KEYS$NL$1"`
			`}`
			`rc_include _all.rc`

			`# Escape double-quote and backslash so they can`
			`# be included as a C-style double-quoted string.`
			`cquote() {`
			`local v="$(xecho "$1" \| sed -e 's,[\"\\],\\&,g' -e 's,$, \\,')"`
			`printf '"%s"' "${v% \\}"`
			`}`

			`(`
docs/cookbook/redoconf-simple: a simple redoconf C++ project. This is a little simpler than the docs/cookbook/c project, which doesn't actually have a doc yet because there was too much to explain. I think I might make that a follow-on cookbook chapter, for people who have read this simple one. I think this doc is maybe a little too long; I intended it to be "here's what you do to get started" but it turned into "here's what you do to get started, and why it works, in excruciating detail." Not quite sure how to fix. (Also updated some other parts of the docs to refer to redoconf as a real thing now instead of a "maybe someone should write this" thing.) 2019-03-05 23:33:11 -05:00			`echo "# Automatically generated by rc_vars.od"`
Experimental new redoconf C/C++ build/autoconfiguration system. To test it out, try this: ./do -j10 build cd docs/cookbook/c redo -j10 test It should detect all the compilers on your system and make three separate builds for each one: normal, debug, and optimized. Then it tries to run a test program under each one. If there are windows cross compilers and you also have 'wine' installed, it'll try running the test program under wine as well. redoconf currently has no documentation other than the example program. We'll fix that later. 2019-02-03 01:14:51 -05:00			`for k in $(echo "$RC_KEYS" \| sort); do`
			`[ "$k" != "RC_INCLUDES" ] \|\| continue`
			`eval v=\$$k`
			`echo "$k=$(shquote "$v")"`
			`done`
			`) >$3`
			`redo-stamp <$3`