When you are to use Windows binaries, skip the step Building and proceed to Windows binaries.

Unpacking source distribution

1. Change directory to where bex1d.zip has been copied.
2. Unzip bex1d.zip as;
   unzip bex1d.zip
3. Source files are unpacked in the newly created directory ./bex1d/source.
4. Sample input files can be found in ./bex1d/sample.

Building

1. Change directory to bex1d/source created by unpacking the source files. (step-3 of above)
2. Investigate sample makefiles and edit one if necessary to fit your environment and platform. Followings are short descriptions of the sample make files:

   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 using a makefile 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

Windows binaries

For Microsoft Windows, for which the building tools are not provided with the system, pre-built binary files are also distributed. Use them as follows:

1. Unpack the pre-built Windows binaries as;
   
   unzip bex1d-win32-binary.zip
2. Binary files as well as the sample input files are unpacked in the newly created directory ./bex1d.
3. It should be noted that, even when to use Windows binary only, the source package bex1d.zip should be unpacked to use sample files in ./bex1d/sample.   Move the binary executable files into ./bex1d/ folder which is the default location of the executables.