Lines Matching refs:on
11 There are various options to build and run OpenSSL on the Windows platforms.
16 Microsoft Visual C++ (MSVC) C compiler on the command line
21 run on the GNU-like development environment MSYS2
22 or run on Linux or Cygwin
24 "Hosted" OpenSSL relies on an external POSIX compatibility layer
63 3. Make sure both Perl and NASM are on your %PATH%
66 choosing one of its variants depending on the intended architecture.
73 <https://docs.microsoft.com/cpp/build/building-on-the-command-line>
78 - `perl Configure VC-WIN64-ARM` if you want Windows on Arm (win-arm64)
80 - `perl Configure VC-WIN64-CLANGASM-ARM` if you want Windows on Arm (win-arm64)
82 - `perl Configure VC-CLANG-WIN64-CLANGASM-ARM` if you want Windows on Arm (win-arm64)
85 on the Universal CRT or
87 on the Universal CRT or
124 for multiple openssl builds to be created and installed on a single system, in
130 A summary table of behavior on Windows platforms
135 |Defined | Undefined |OpenSSL returns errors on module/conf load|
178 * Usually the build is done on Windows in a GNU-like environment called MSYS2.
183 The resulting OpenSSL does not rely on MSYS2 to run and is fully native.
194 These compilers must be on your MSYS2 $PATH.
195 A common error is to not have these on your $PATH.
198 In the MSYS2 shell do the configuration depending on the target architecture:
214 * It is also possible to build mingw[64] on Linux or Cygwin.
225 This requires that you've installed the necessary add-on packages for
245 relying on `USER32.DLL`. E.g., on Windows Vista and later you could:
264 Cygwin implements a POSIX/Unix runtime system (`cygwin1.dll`) on top of the
