Lines Matching +full:linux +full:- +full:intel
10 Developing HPC software is more difficult on Microsoft Windows than Linux and macOS systems.
16 - {any}`sec_linux_on_windows`
17 - {any}`sec_cygwin_gnu_on_windows`
18 - {any}`sec_native_compilers_on_windows`
19 - {any}`sec_msys2_mingw_compilers_on_windows`
25 ## Linux on Microsoft Windows
27 - Microsoft Windows Subsystem for Linux 2 ([WSL2](https://docs.microsoft.com/en-us/windows/wsl/inst…
28 - [Docker](https://docs.docker.com/docker-for-windows/) for Microsoft
30 - Linux virtual machine via [VirtualBox](https://www.virtualbox.org/) or similar. One sample
41 that work on Microsoft Windows, with Cygwin pre-built libraries for BLAS, LAPACK, and Open MPI.
48 - python3
49 - make
50 - gcc-core gcc-g++ gcc-fortran
51 - liblapack-devel
52 - openmpi libopenmpi-devel libhwloc-devel libevent-devel zlib-devel
63 - Libraries built with Cygwin/GNU compilers are **not** compatible and cannot be linked with Micros…
64 - Native libraries like MS-MPI, Intel MPI cannot be used from Cygwin/GNU compilers.
65 - Most {ref}`external packages <doc_externalsoftware>` are likely to work,
66 however the `configure` option `--download-mpich` does not work.
73 ## Native Microsoft/Intel Windows Compilers
76 the native Microsoft/Intel compilers behave differently than other (Unix) compilers. So to
77 install PETSc on Microsoft Windows with Microsoft or Intel compilers one has to install Cygwin (for…
78 and use `win32fe` [^win32] compiler wrapper, to use the Microsoft/Intel compilers.
85 - python3
86 - make
93 Cygwin link.exe can conflict with Intel ifort compiler. If you are using ifort -
97 $ mv /usr/bin/link.exe /usr/bin/link-cygwin.exe
103 `cl foo.c` or `ifort foo.F` works from this shell. For example - if using `Visual Studio 2022 C`
104 and `Intel oneAPI 2022 Fortran`, one can do:
106 …1. `Start` -> `Programs` -> `Intel oneAPI 2022` -> `Intel oneAPI command prompt for Intel 64 for V…
109 2. Within this `DOS Command shell` - run `Cygwin64 Terminal`, i.e., `mintty.exe` as:
112 C:\cygwin64\bin\mintty.exe -
122 Use `configure` with `Visual Studio 2022 C` and `Intel oneAPI 2022 Fortran` (without MPI):
125 $ ./configure --with-cc='win32fe_cl' --with-fc='win32fe_ifort' --with-cxx='win32fe_cl' --with-mpi=0…
131 $ ./configure --with-cc='win32fe_cl' --with-fc=0 --with-cxx=0 --download-f2cblaslapack
135 - One can use Intel oneAPI C/C++ compiler `icl` or `icx` instead of Microsoft `cl`, for ex: `--with…
136 - A shorter form `--with-cc=cl` that translates to `--with-cc=win32fe_cl` is also supported. Simila…
137 - Intel oneAPI `ifx` currently works with `--with-shared-libraries=0` only, `ifort` is recommended …
138 - The `--download-package` option may work with some {ref}`external packages <doc_externalsoftware>…
143 We support both MS-MPI (64-bit) and Intel MPI on Microsoft Windows. We also support using Intel MKL…
144 For example usages, check `$PETSC_DIR/config/examples/arch-mswin*.py`
150 Microsoft Windows - this usually affects specifying MPI or MKL. Microsoft Windows
151 supports DOS short form for directory names - so it is better to use this notation. Cygwin
155 $ cygpath -u `cygpath -ms '/cygdrive/c/Program Files (x86)/Microsoft SDKs/MPI'`
157 $ cygpath -u `cygpath -ms '/cygdrive/c/Program Files (x86)/IntelSWTools/compilers_and_libraries/win…
164 $ ./configure --with-cc='win32fe_cl' --with-fc='win32fe_ifort' --with-cxx='win32fe_cl' \
165 --with-shared-libraries=0 \
166 --with-mpi-include='[/cygdrive/c/PROGRA~2/MICROS~2/MPI/Include,/cygdrive/c/PROGRA~2/MICROS~2/MPI/In…
167 --with-mpi-lib='-L/cygdrive/c/PROGRA~2/MICROS~2/MPI/lib/x64 msmpifec.lib msmpi.lib' \
168 --with-mpiexec=/cygdrive/c/PROGRA~1/MICROS~2/Bin/mpiexec \
169 --with-blaslapack-lib='-L/cygdrive/c/PROGRA~2/INTELS~1/COMPIL~2/windows/mkl/lib/intel64 mkl_intel_l…
178 different for each build of PETSc. So if you need a project file for use with PETSc -
184 2. Try compiling the example from Cygwin bash shell - using `make` - i.e.:
191 3. If the above works - then make sure all the compiler/linker options used by `make`
194 4. If errors - redo the above step. If all the options are correctly specified, the
204 applications that are compatible with the Microsoft and Intel compilers.
206 1. Install MSYS2 and MS-MPI:
209 … to use MPI, we recommend you use MS-MPI from <https://learn.microsoft.com/en-us/message-passing-i…
213 First, launch a MSYS2 MinGW x64 shell. Double-check this is the proper type of shell by typing
222 installation using `pacman` (you may be asked to quit and re-open your shell).
225 $ pacman -Syu
232 $ pacman -S autoconf automake-wrapper bison bsdcpio make git \
233 mingw-w64-x86_64-toolchain patch python flex \
234 pkg-config pkgfile tar unzip mingw-w64-x86_64-cmake \
235 mingw-w64-x86_64-msmpi mingw-w64-x86_64-openblas mingw-w64-x86_64-jq
240 …re more than one available in a MSYS2 MinGW shell and 2) tell PETSc where MS-MPI `mpiexec` is. We …
243 $ /usr/bin/python ./configure --with-mpiexec='/C/Program\ Files/Microsoft\ MPI/Bin/mpiexec' \
244 --with-shared-libraries=0
253 Running PETSc programs with `-start_in_debugger` is not supported on Microsoft Windows. Debuggers n…
261 Intel Enhanced Debugger:
277 and Intel compilers and associated tools - to enable building PETSc libraries using
279 `${PETSC_DIR}/lib/petsc/bin/win32fe/win32fe --help`