5c4f710f4e
This makes them more reliable to parse. redo-log can parse each line, format and print it, then recurse if necessary. This got a little ugly because I wanted 'redo --raw-logs' to work, which we want to format the output nicely, but not call redo-log. (As a result, --raw-logs has a different meaning to redo and redo-log, which is kinda dumb. I should fix that.) As an added bonus, redo-log now handles indenting of recursive logs, so if the build was a -> a/b -> a/b/c, and you look at the log for a/b, it can still start at the top level indentation.
22 lines
564 B
Python
Executable file
22 lines
564 B
Python
Executable file
#!/usr/bin/env python2
|
|
import sys, os
|
|
import vars, state
|
|
from logs import err
|
|
|
|
|
|
try:
|
|
me = os.path.join(vars.STARTDIR,
|
|
os.path.join(vars.PWD, vars.TARGET))
|
|
f = state.File(name=me)
|
|
for t in sys.argv[1:]:
|
|
if not t:
|
|
err('cannot build the empty target ("").\n')
|
|
sys.exit(204)
|
|
if os.path.exists(t):
|
|
err('redo-ifcreate: error: %r already exists\n' % t)
|
|
sys.exit(1)
|
|
else:
|
|
f.add_dep('c', t)
|
|
state.commit()
|
|
except KeyboardInterrupt:
|
|
sys.exit(200)
|