Directory reorg: move code into redo/, generate binaries in bin/.
It's time to start preparing for a version of redo that doesn't work unless we build it first (because it will rely on C modules, and eventually be rewritten in C altogether). To get rolling, remove the old-style symlinks to the main programs, and rename those programs from redo-*.py to redo/cmd_*.py. We'll also move all library functions into the redo/ dir, which is a more python-style naming convention. Previously, install.do was generating wrappers for installing in /usr/bin, which extend sys.path and then import+run the right file. This made "installed" redo work quite differently from running redo inside its source tree. Instead, let's always generate the wrappers in bin/, and not make anything executable except those wrappers. Since we're generating wrappers anyway, let's actually auto-detect the right version of python for the running system; distros can't seem to agree on what to call their python2 binaries (sigh). We'll fill in the right #! shebang lines. Since we're doing that, we can stop using /usr/bin/env, which will a) make things slightly faster, and b) let us use "python -S", which tells python not to load a bunch of extra crap we're not using, thus improving startup times. Annoyingly, we now have to build redo using minimal/do, then run the tests using bin/redo. To make this less annoying, we add a toplevel ./do script that knows the right steps, and a Makefile (whee!) for people who are used to typing 'make' and 'make test' and 'make clean'.
This commit is contained in:
parent
5bc7c861b6
commit
f6fe00db5c
140 changed files with 256 additions and 99 deletions
16
docs/cookbook/hello/hello.do
Normal file
16
docs/cookbook/hello/hello.do
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
# If hello.c changes, this script needs to be
|
||||
# re-run.
|
||||
redo-ifchange hello.c
|
||||
|
||||
# Compile hello.c into the 'hello' binary.
|
||||
#
|
||||
# $3 is the redo variable that represents the
|
||||
# output filename. We want to build a file
|
||||
# called "hello", but if we write that directly,
|
||||
# then an interruption could result in a
|
||||
# partially-written file. Instead, write it to
|
||||
# $3, and redo will move our output into its
|
||||
# final location, only if this script completes
|
||||
# successfully.
|
||||
#
|
||||
cc -o $3 hello.c -Wall
|
||||
Loading…
Add table
Add a link
Reference in a new issue