Difference between revisions of "Building on Windows"
From GridPACK
| Line 19: | Line 19: | ||
* [https://msdn.microsoft.com/en-us/library/windows/desktop/bb524831%28v=vs.85%29.aspx Microsoft MPI] <br/> This appears to be the only modern implementation available for Windows. In the past, the OpenMPI and MPICH implementation were available for Windows, but no more. | * [https://msdn.microsoft.com/en-us/library/windows/desktop/bb524831%28v=vs.85%29.aspx Microsoft MPI] <br/> This appears to be the only modern implementation available for Windows. In the past, the OpenMPI and MPICH implementation were available for Windows, but no more. | ||
* (optional) [https://www.microsoft.com/en-us/download/details.aspx?id=48215 MS-MPI Debugger Extension] is useful for debugging problem with parallel programs. | * (optional) [https://www.microsoft.com/en-us/download/details.aspx?id=48215 MS-MPI Debugger Extension] is useful for debugging problem with parallel programs. | ||
| + | * Choose a place to install libraries. <tt>C:\GridPACK</tt> is used in this case. | ||
= Build Required Libraries = | = Build Required Libraries = | ||
== Boost == | == Boost == | ||
| + | |||
| + | == BLAS/LAPACK (CLAPACK) == | ||
| + | |||
| + | Some implementation of BLAS/LAPACK is required for PETSc and some other libraries. The implementation described here was chosen because it does not require a Fortran compiler. It is apparently ''really'' slow. It will probably be necessary to install Intel compilers and MKL in order to get improvement in speed. The Windows port of CLAPACK is described [http://icl.cs.utk.edu/lapack-for-windows/clapack/ here]. | ||
| + | * Get the source [http://icl.cs.utk.edu/lapack-for-windows/clapack/clapack-3.2.1-CMAKE.tgz here]. | ||
| + | * Configure, build, and install | ||
| + | set prefix="C:\GridPACK" | ||
| + | cmake -Wdev ^ | ||
| + | -G "Visual Studio 10 2010 Win64" ^ | ||
| + | -D CMAKE_INSTALL_PREFIX:PATH="%prefix%" ^ | ||
| + | .. | ||
| + | cmake --build . --config Release | ||
| + | cmake --build . --target install --config Release | ||
| + | |||
| + | == SuiteSparse == | ||
| + | |||
| + | == PETSc == | ||
== Global Arrays == | == Global Arrays == | ||
| − | |||
| − | |||
Revision as of 17:57, 6 December 2016
Building GridPACK on Windows is not for the faint of heart.
Contents
System Preparation
The following are available as native Windows applications and can just be installed in the normal Windows way:
- Visual C++ in some form.
- The "free" ones, Visual Studio Express and Community, should work.
- Windows SDK
Usually, this is just installed with Visual Studio - CMake is required
- A minimal Cygwin installation is necessary.
Cygwin is required to build, and test for, PETSc. If the system has a Cygwin installation that is being used, it would probably be best to make another installation for GridPACK installation exclusively.- Minimum required packages:
- Base
- Python
- Rename /usr/bin/link.exe so it does not interfere with Windows LINK.EXE
- If you want to use a Cygwin shell to build and/or debug GridPACK applications:
- Do not install a compiler set.
- Do not install CMake.
- Minimum required packages:
- Microsoft MPI
This appears to be the only modern implementation available for Windows. In the past, the OpenMPI and MPICH implementation were available for Windows, but no more. - (optional) MS-MPI Debugger Extension is useful for debugging problem with parallel programs.
- Choose a place to install libraries. C:\GridPACK is used in this case.
Build Required Libraries
Boost
BLAS/LAPACK (CLAPACK)
Some implementation of BLAS/LAPACK is required for PETSc and some other libraries. The implementation described here was chosen because it does not require a Fortran compiler. It is apparently really slow. It will probably be necessary to install Intel compilers and MKL in order to get improvement in speed. The Windows port of CLAPACK is described here.
- Get the source here.
- Configure, build, and install
set prefix="C:\GridPACK"
cmake -Wdev ^
-G "Visual Studio 10 2010 Win64" ^
-D CMAKE_INSTALL_PREFIX:PATH="%prefix%" ^
..
cmake --build . --config Release
cmake --build . --target install --config Release
