nawips54src.README This is the source code distribution of NAWIPS 5.4. The source code and pre-compiled libraries are found in the file nawips54src.tar.Z. NOTE: The pre-compiled GEMPAK libraries are included in this distribution. If all you want to do is link the GEMPAK libraries into your own program, YOU DO NOT HAVE TO BUILD (run make) THE NAWIPS SOFTWARE. All you have to do is untar this distribution. The libraries will be located in the directory $NAWIPS/lib/hpux/. The source code distribution is NOT REQUIRED to run NAWIPS. It is being made available here for those advanced users who would like to use the source code. Since GEMPAK source code is very well documented, some advanced users might like to peruse it for insight into their work with GEMPAK, or perhaps even use certain routines for work outside of GEMPAK. Some advanced users may even want to do further GEMPAK development, such as tweaking code here and there to modify it's behavior, or to use it as a model for writing new GEMPAK programs or functionality. This source distribution is intended to complement the binary distribution of NAWIPS 5.2.1 available in the files: nawips/NAWIPS.install.README nawips/newfeatures54.README nawips/nawips54soo.tar.Z nawips/gempakdir54.tar.Z nawips/sampledata.tar.Z The source distribution, contrib/nawips54src.tar.Z, does not contain any binaries or sample data files. I strongly encourage you to first install the binary distribution from the above files, then apply the source distribution. To unpack the source distribution, download the nawips521src.tar.Z file and put it in the top level NAWIPS directory tree, (/usr1/nawips for most SACs): % mv nawips54src.tar.Z /usr1/nawips % cd /usr1/nawips % zcat nawips54src.tar.Z | tar xvf - Now, the source distribution has been added to your binary distribution, and now you have a full NAWIPS/GEMPAK distribution. The NAWIPS 5.4 source distribution comes with Makefiles for easy compilation and linking. "make" is a UNIX utility that automates the compilation, linking, and installation of software. "make" is directed by a file, usually called "Makefile" that resides in the source directory. You will find that you are usually asked to run make when installing any application software. (You didn't have to do this when you got the binary distribution of NAWIPS, because I did it for you.) One thing to remember about "make", "make" is only as good as the "Makefiles", so installation can be smooth or rocky depending on who wrote the "Makefiles". You can use the NAWIPS Makefiles at any place in the distribution. If you use make at the top level (the $NAWIPS/ directory) you will completely recompile and re-link the entire NAWIPS distribution. You can also use make at any subdirectory level. At any subdirectory level, you will recompile only those programs or libraries in the subdirectory or below. This is called "recursive make" for the UNIX-philes. The Makefiles are very easy to use. There are only a couple of things you must know: 1) In your file ~gempak/Common.cshrc, you will find a section that looks like this: # # If you will be building GEMPAK or NAWIPS from source # uncomment the following commands to read in the compilation # and linking definitions. # #if ( ! -e $GEMPAKUSER/Install.cshrc ) then # echo "Can not find Install.cshrc file" # echo "Do not try to compile NAWIPS/GEMPAK" #else # source $GEMPAKUSER/Install.cshrc #endif By default, this IF-ELSE-ENDIF section is commented out. If you intend to use the Makefiles, you must uncomment this section. It will not change your environment very much, it will simply "source" another file, Install.cshrc, which sets up a few standard environment variables used in compilation. After uncommenting these lines, re-source the Common.cshrc file: % source ~gempak/Common.cshrc Next time you log in, this will be done for you automatically. 2) There is one Makefile in each directory of NAWIPS that requires compilation and/or linking. (As of now, there are over 150 of these Makefiles!) Each Makefile refers to a single configuration file, /usr1/nawips/config/Makeinc.common (or if you're in the GEMPAK source code, $NAWIPS/gempak/Gempak.include which refers to /usr1/nawips/config/Makeinc.common). The Makeinc.common file then refers to a platform specific file. For the SACs, that file is /usr1/nawips/config/Makeinc.hpux. This file sets up the specific information needed for compiling and linking NAWIPS on an HP. You shouldn't need to edit any of these files, but if something goes wrong in your recompilation, you may want to check the settings made in the files /usr1/nawips/config/Makeinc.common and /usr1/nawips/config/Makeinc.hpux. 3) To run "make", there are only a few commands you must know. They are called "targets": % make all % make install % make clean These are the standard targets. "make all" will compile and/or link the software. "make install" will install the newly created binaries in your /usr1/nawips/exe/hpux directory. "make clean" will clean out the directories of any links, ".o", or ".a" files. (These things are created in the process of the "make all" step. There is an advantage to keeping them around until you are finished installing the software.) "make all" and "make install" are usually required for any task. "make clean" is usually optional. There is one other important target in the NAWIPS Makefiles: % make programs_nc This target builds "_nc" versions of the programs, such as "gdcntr_nc" and "gdplot_nc". These programs are often used in metafile generation scripts. 4) A final word about running "make". If your system encounters any errors in the "make" process, the process will stop. Thus, if you run "make" and it does not finish cleanly, you might need to look closely at any error messages that appear. In order to do this, I always recommend that you run the "make" targets and collect the output in a log file: % make all >& all.out & % make programs_nc >& programs.out & % make install >& install.out & % make clean >& clean.out & Each of these commands will log all the output from the "make" process in a file (all.out, or programs.out, etc.). You can then examine these files later to debug any problems in the installation. If you consult with me about problems with "make", be assured that I will ask you for a copy of the ".out" log. To watch the messages as they are being logged in the ".out" file, use the "tail" command: % tail -f all.out To interrupt this command, use Cntrl-C. That's all you need to know about "make" and the NAWIPS Makefiles. If you have any questions, don't hesitate to ask. __________________________________________________________________ Peggy Bruehl National SAC Coordinator - NWS peggy@comet.ucar.edu COMET/UCAR PO Box 3000 (303) 497-8356 Boulder, CO 80307-3000 SOO/SAC Home Page: http://www.comet.ucar.edu/pub_html/sac_html/index.html ------------------------------------------------------------------