|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: N T
Length: 4995 (0x1383) Types: TextFile Names: »NOTE-Spiderweb«
└─⟦52210d11f⟧ Bits:30007239 EUUGD2: TeX 3 1992-12 └─⟦63303ae94⟧ »unix3.14/TeX3.14.tar.Z« └─⟦c58930e5c⟧ └─⟦this⟧ »TeX3.14/Spiderweb/NOTE-Spiderweb«
[This file is ./TeX3.1/Spiderweb/NOTE-Spiderweb. It is intended for users of the UNIX TeX distribution. April 1991.] ----------------------------------------------- Note that the Makefile states explicitly that things have been set up for SUN o.s. 4. We did a test-run on our SUN2/120, SUN o.s. 3.5, and were able to make tangles, weaves, and *web.tex macros for ada, awk, c, c++, dijkstra, larch, penelope, and ssl; i.e., all languages covered by Spidery WEB. ----------------------------------------------- The following sketch is intended as a supplement to the primary README file in this directory. Sketch of Installation Process: ============================== 1. If you are not familiar with Spidery WEB, you may wish to start out by printing out the documentation for it. You will need to have TeX and LaTeX up and running on your system. Copy the file webkernel.tex to your TEXINPUTS directory (or to ./doc; i.e. whatever is to function as your current directory when you run the doc files through tex) so that TeX will be able to find it. Go to the directory doc, and tex abstracts.tex and spiderwebman.tex; latex cacm.tex, overview.tex, spiderman.tex; print the .dvi files. 2. Go to the directory master; edit the WebMakefile. Be sure to define the following correctly to suit your site, and be sure to end each definition below with a pound sign (#) to make certain that no extra space is inserted after it: HOME= WEBROOT=[the path to your ./Spiderweb directory] CPUTYPE=[If you do not have a cputype program, and if it is important in your environment to distinguish between different cpu types, define this simply as CPUTYPE=cputype with no quotation marks around it; then, write a script named "cputype" consisting of the following two lines: #!/bin/sh echo 'sun2' Define your cpu type as whatever it is; ours is a sun2. Place this script in your WEBROOT directory; make certain that it is executable in mode; and be certain that WEBROOT is on your path, or make will not be able to find your cputype script. Also, be sure to create a subdirectory in the directory master, and call it "sun2" or whatever your cpu type is. This is where the common object files will be copied. If you have no need to distinguish between cpu types, comment out the CPUTYPE= line, and comment out or delete $(CPUTYPE) wherever it occurs in this WebMakefile. Make certain, however, that MASTER and OBDIR are not the same directory. For OBDIR, make up a subdirectory (call it whatever you wish) in the directory called master to which the common object files can be copied. Be sure to create this directory, or make will not be able to find it.] DEST=[where the executables are to be placed] MACROS=[where the adaweb.tex, awkweb.tex, cweb.tex, etc. macros are to be placed during the course of "make all"; TeX must be able to find them.] 3. Place yourself in the top-level Spiderweb directory (i.e., in WEBROOT), and type the following at your prompt: % make boot This will make ceetangle and awktangle, and will place them in your DEST directory. 4. You are now ready to make all. Make certain that your DEST directory is on your path, or make will not be able to find the ceetangle and ceeweave it needs in order to make tangles and weaves for each of the languages in which you plan to write webbed programs. In the top-level Spiderweb Makefile, go to the line that defines DIRECTORIES. Make a copy of that line immediately below itself. Comment out the original line (by placing a pound sign at the beginning of it), and edit the copied line by deleting the directory names doc and master (because during your make all, it will not make sense for doctangles and docweaves, etc., to be made, and the make will fail). Also delete the names of languages for which you will not be writing WEB files, for which you will have no need for tangles and weaves. At your prompt, type: % make all This will make a tangle and a weave for each of the languages you defined (for example, if you defined ada on your DIRECTORIES= line, an adatangle and an adaweave will be made). They will be placed in your DEST directory. The *web.tex macro files for each of the languages defined (e.g., adaweb.tex, awkweb.tex, etc.) will also be made and placed in whatever you defined as your MACROS directory in your ./master/WebMakefile. You are now ready to write webbed programs (i.e., programs using the WEB system of documentation) in Ada, C, C++, or whatever language you selected above. And you will be able to tangle them for compilation to make an executable for your machine, and you will be able to weave them to produce documentation (*.tex) files for processing by TeX. ============================EOF==============================