Lines Matching +full:vc +full:- +full:win32

6  directly, and "hosted" which rely on POSIX-compatible layer. "Native"
7  targets are VC-* (where "VC" stems from abbreviating Microsoft Visual C
11  are always cross-compiled. On Linux and Cygwin they look exactly as such
12  and require --cross-compile-prefix option. While on MSYS[2] it's solved
15  emulated filesystem name space with POSIX-y root, mount points, /dev
18  start, and if it's found *not* to be linked with MSYS2 POSIX-y thing,
21  'c:\some\where', '/dev/null' - 'nul'. This creates an illusion that
24  system in exactly same way as one produced by VC, and in its essence
29  Visual C++ builds, aka VC-*
33  -------------------
38  - Perl. We recommend ActiveState Perl, available from
44  - Microsoft Visual C compiler. Since we can't test them all, there is
48    falls into best-effort category.
50  - Netwide Assembler, aka NASM, available from https://www.nasm.us,
53    64-bit version is exercised through continuous integration of
54    VC-WIN64A-masm target.
58  ------------------------
63  For VC-WIN32, the following defaults are use:
68  For VC-WIN64, the following defaults are use:
73  Should those environment variables not exist (on a pure Win32
81  start the command prompt by right-clicking on it and choosing "Run as
84  --prefix and --openssldir when configuring.
93    needed,) mingw-w64-i686-gcc and/or mingw-w64-x86_64-gcc. You should
100    configuring with corresponding --cross-compile-prefix= option. For
103      ./Configure mingw --cross-compile-prefix=i686-w64-mingw32- ...
107      ./Configure mingw64 --cross-compile-prefix=x86_64-w64-mingw32- ...
109    This naturally implies that you've installed corresponding add-on
113  paths are similar to those used when building with VC-* targets, except
155  OpenSSL BIO layer and your compiler run-time. See the OPENSSL_Applink
178  mounted as text (i.e. mount -t c:\somewhere /home) due to Cygwin
180  mount is used, e.g. mount -b c:\somewhere /home.