Operations of PADE during parallel development



next up previous contents
Next: PADE Installation and Up: How PADE Works Previous: The anatomy of

Operations of PADE during parallel development

 

The two ways in which PADE aids the parallel developer are by helping to keep track of which source files must be sent and compiled on which hosts and by actually sending the files and issuing the compile commands. In the PADE development model, the developer keeps all source files on a single host (the development host) and is required to enter the names of the hosts, the files needed to build the binary on each host, and the commands required to build the binary on each host. This information is referred to in the rest of this manual as the setup information.

Once the setup information has been entered, the developer begins the edit/transfer/compile/execute cycle described earlier. In the edit phase, PADE enables the developer to modify any file described in the setup information with a user-specified editor. PADE enables the developer to complete the transfer and compile phases in one step. PADE uses the PVM program pvmmake (provided in the PADE distribution) to perform these steps. This program can send a file to any host and issue any command on any host and takes its orders from a pvmmake ``config file''. PADE translates the setup information into pvmmake commands and writes a config file. It then executes pvmmake with this config file to affect the transfer and compilation. The developer launches these operations with a click of the mouse. PADE also exhibits the results of the compilations on the various hosts in a display window that can be scrolled through at leisure and saved if desired. In the execution phase, PADE enables the developer to launch the application being developed and to view the output in a display window.




Fri Mar 31 20:30:34 EST 1995