Building

HFRD VMS Hypertext Services ... read this first

| [next] [previous][contents]


5 - Building




1 All of the applications are written in C.

? As the software has been written to the requirements of DEC C J(in an uncritical, VAXC-backward-compatible compilation mode, i.e. 7/STANDARD=VAXC (when moving from VAXC C to HDEC C the author discovered he wasn't the rigorous software engineer he :had hoped he was :^)) its build and run-time ;behaviour in other compiler environments is unpredictable. 

/ All applications are linked against the DEC C >DECC$SHR.EXE RTL. The DEC C run-time environment is Hprefered to the VAX C run-time environment because the former's greater Eintegrity and improved performance over the latter. See the section OExecutables for further information on this Icomponent. In all probability, if you're considering re-compiling, this >environment will already be available on your site somewhere. 

C Brute-force build procedures are provided in each software .application source directory. They are named ``BUILD_whatever.COM''.

I Two procedures can be used to rebuild or relink all applications in the Npackage. Because of some dependencies the HTTPd server should be built first.

 

F Also, the HTTPd server itself is specifically tailored to DEC TCP/IP NServices for OpenVMS (primarily) and TGV MultiNet (secondarily), particularly Itheir QIO interfaces, so again its build and run-time behaviour in other Menvironments is indeterminate. The HTTPd server build procedure detects the EMultiNet environment and builds accordingly. The executable in this Aenvironment is specifically named HTTPD_MULTINET.EXE so Has to clearly indicate which build has occured. This can be renamed to @HTTPD.EXE or left unchanged and procedures modified to reflect that name. 




| [next] [previous][contents]