How to Make Binaries?
Click here to go to Parafrase-2 home page.
New "make" procedure (Recommended)
Use "make". Make sure your "make" can handle ${OBJ:.o=.c} style of
string substitution. You may try "make maketest" in your source
directory, where you have bunch of sub-directories such as alias,
analyze, etc. If your make complains or generates nothing, hard luck.
You'll need to edit most of the Makefiles in the sub-directories.
${OBJ:.o=.c} style is used rather extensively. We are accepting your
donation of scripts which automatically replace ${OBJ:.o=.c} style to
the appropriate list of the file names. If your make prints "abc.X",
you are lucky enough.
Before making binaries, you may wish to define ${CC} and ${CFLAGS} of
your favorite. It may be a good idea to define ${P2CODEDIR}
explicitly. You may do this from your command line ("man make" for
detail), or you may edit the Makefile in the source directory.
After you finished your setup, just run "make" with appropriate
targets. My favorite is of course, just "make".
Old "make" procedure (Still available for transition)
Use your beloved "mymake".
- mymake f for p2fpp (Fortran version)
- mymake c for p2cpp (C version)
- mymake f2c for p2f2c (F2C version)
- mymake f g for p2fppg (Fortran version with X11 interface)
Last Update: July 10, 1994
Questions? Send e-mail to Hideki Saito (saito@csrd.uiuc.edu)