|
NAMEmakeppreplay -- Fast repeater of selected makepp actionsDESCRIPTION?: -?, A: -A, --args-file, --arguments-file, C: -C, -c, D: --directory, --dry-run, H: -h, --help, I: -I, --include, --include-dir, J: --just-print, K: -k, --keep-going, M: -M, $MAKEPPREPLAYFLAGS, --module, N: -n, --no-print-directory, --no-warn, R: --recon, --root-dir, --root-directory, T: -t, --temporary, V: -V, --versionmakeppreplay [ option ... ] [ VAR=value ] [ target ... ] mppr [ option ... ] [ VAR=value ] [ target ... ] Makeppreplay tries to do the same things makepp did. It does this solely based on the remembered build info, saving much time by not reading makefiles, not parsing commands, not scanning files and not looking at every repository file, to see whether it fits. But unlike makepp it reuses all repository links it finds. It does not know about phony or default targets, so you have to give it real files or directories, as a shortcut for all files makepp has built therein. By default it builds all files makepp built in the current or chosen directory. This approach is only correct when there are no structural changes, i.e. no different modules to be linked, no moved files, no different "#include" statements, which should possibly have caused those files to be (re)built. After updating from version control, or when building against a repository, where others may have caused such changes, you should call makepp once after potential changes (e.g. in the morning after an overnight repository update), to be sure your build infos are up to date. Not reading makefiles means, it will not know any subs (Perl functions) defined in them. For this you should put all your functions into an external module. It will also not know about any variable settings, which is only a problem if your Perl code accesses them (because in rule actions they have already been expanded). TODOThis is still experimental and imperfect.
OPTIONSOptions include some of the makepp options, plus two new ones, for loading modules that would normally be loaded from a makefile.
EXAMPLESProbably the most common use is relinking either a program or a library after editing a source file:makeppreplay subdir/foo.o bin/bar mppr subdir/foo.o lib/libbar.so ENVIRONMENTMakeppreplay looks at the following environment variable:
AUTHORDaniel Pfeiffer (occitan@esperanto.org)
Visit the GSP FreeBSD Man Page Interface. |