When you are to use Windows binaries, skip first two steps (Unpacking and Building) and proceed to Windows binaries.

Unpacking

1. Change directory to where gpop.zip has been copied.
2. Unzip gpop.zip as;
   unzip gpop.zip
3. GPOP source files are unpacked in the newly created directory ./gpop/source.
4. GPOP sample input files can be found in ./gpop/sample.
5. HTML document files can be found in ./gpop/doc.

Building

1. Change directory to gpop/source created when gpop source files are unpacked. (step-3 of above)
2. Investigate the sample makefiles, choose one, and edit it to fit your environment, if necessary.  Followings are short descriptions of sample makefiles.

   makeGnu.make		for GNU compilers on Unix-like platforms
   makeIntel64oapiLinux.make		for Intel oneAPI 2025 & later on Linux
   makeIntel64oapiLinuxMKL.make		for Intel oneAPI 2025 & later on Linux (static link with sequential MKL)
   makeIntel64oapiWin.make		for Intel oneAPI 2025 & later on Windows
   makeIntel64oapiWinMKL.make		for Intel oneAPI 2025 & later on Windows (static link with sequential MKL)
   makeIntelLinux.make		for Intel compilers on Linux
   makeIntelWin.make		for Intel compilers on Windows

3. On Unix-like platforms, build executables by 'make' as
   
   make -f makefile-name
   On genuine Windows development environment, use 'nmake' command as
   
   nmake -f makefile-name
4. Remove temporary files as
   (n)make -f makefile-name clean
5. Install executable files as
   (n)make -f makefile-name install

Windows binaries

1. Using the built-in tool on Windows, unpack the pre-built Windows binaries (gpop-win32-binary.zip).   You may use other unpacking tools if you like.
2. Binary executable files can be found in the folder, gpop-win32-binary.   Note that the location of this folder depends on how you unplack the archive.
3. Unpack the source package (gpop.zip) to use sample input files.   Move the binary executable files into gpop folder which is the default location of the executables.