VirtualBox

source: vbox/trunk/src/libs/openssl-3.3.2/NOTES-WINDOWS.md

最後變更 在這個檔案是 108206,由 vboxsync 提交於 4 週 前

openssl-3.3.2: Exported all files to OSE and removed .scm-settings ​bugref:10757

  • 屬性 svn:eol-style 設為 native
  • 屬性 svn:keywords 設為 Author Date Id Revision
檔案大小: 9.5 KB
 
1Notes for Windows platforms
2===========================
3
4 - [Native builds using Visual C++](#native-builds-using-visual-c)
5 - [Native builds using Embarcadero C++Builder](
6 #native-builds-using-embarcadero-cbuilder)
7 - [Native builds using MinGW](#native-builds-using-mingw)
8 - [Linking native applications](#linking-native-applications)
9 - [Hosted builds using Cygwin](#hosted-builds-using-cygwin)
10
11There are various options to build and run OpenSSL on the Windows platforms.
12
13"Native" OpenSSL uses the Windows APIs directly at run time.
14To build a native OpenSSL you can either use:
15
16 Microsoft Visual C++ (MSVC) C compiler on the command line
17or
18 Embarcadero C++Builder
19or
20 MinGW cross compiler
21 run on the GNU-like development environment MSYS2
22 or run on Linux or Cygwin
23
24"Hosted" OpenSSL relies on an external POSIX compatibility layer
25for building (using GNU/Unix shell, compiler, and tools) and at run time.
26For this option, you can use Cygwin.
27
28Native builds using Visual C++
29==============================
30
31The native builds using Visual C++ have a `VC-*` prefix.
32
33Requirement details
34-------------------
35
36In addition to the requirements and instructions listed in `INSTALL.md`,
37these are required as well:
38
39### Perl
40
41We recommend Strawberry Perl, available from <http://strawberryperl.com/>
42Please read NOTES.PERL for more information, including the use of CPAN.
43An alternative is ActiveState Perl, <https://www.activestate.com/ActivePerl>
44for which you may need to explicitly build the Perl module Win32/Console.pm
45via <https://platform.activestate.com/ActiveState> and then download it.
46
47### Microsoft Visual C compiler.
48
49Since these are proprietary and ever-changing we cannot test them all.
50Older versions may not work. Use a recent version wherever possible.
51
52### Netwide Assembler (NASM)
53
54NASM is the only supported assembler. It is available from <https://www.nasm.us>.
55
56Quick start
57-----------
58
59 1. Install Perl
60
61 2. Install NASM
62
63 3. Make sure both Perl and NASM are on your %PATH%
64
65 4. Use Visual Studio Developer Command Prompt with administrative privileges,
66 choosing one of its variants depending on the intended architecture.
67 Or run `cmd` and execute `vcvarsall.bat` with one of the options `x86`,
68 `x86_amd64`, `x86_arm`, `x86_arm64`, `amd64`, `amd64_x86`, `amd64_arm`,
69 or `amd64_arm64`.
70 This sets up the environment variables needed for `nmake.exe`, `cl.exe`,
71 etc.
72 See also
73 <https://docs.microsoft.com/cpp/build/building-on-the-command-line>
74
75 5. From the root of the OpenSSL source directory enter
76 - `perl Configure VC-WIN32` if you want 32-bit OpenSSL or
77 - `perl Configure VC-WIN64A` if you want 64-bit OpenSSL or
78 - `perl Configure VC-WIN64-ARM` if you want Windows on Arm (win-arm64)
79 OpenSSL or
80 - `perl Configure VC-WIN64-CLANGASM-ARM` if you want Windows on Arm (win-arm64)
81 OpenSSL with assembly support using clang-cl as assembler or
82 - `perl Configure VC-CLANG-WIN64-CLANGASM-ARM` if you want Windows on Arm (win-arm64)
83 OpenSSL using clang-cl as both compiler and assembler or
84 - `perl Configure VC-WIN32-HYBRIDCRT` if you want 32-bit OpenSSL dependent
85 on the Universal CRT or
86 - `perl Configure VC-WIN64A-HYBRIDCRT` if you want 64-bit OpenSSL dependent
87 on the Universal CRT or
88 - `perl Configure` to let Configure figure out the platform
89
90 6. `nmake`
91
92 7. `nmake test`
93
94 8. `nmake install`
95
96For the full installation instructions, or if anything goes wrong at any stage,
97check the INSTALL.md file.
98
99Installation directories
100------------------------
101
102The default installation directories are derived from environment
103variables.
104
105For VC-WIN32, the following defaults are use:
106
107 PREFIX: %ProgramFiles(x86)%\OpenSSL
108 OPENSSLDIR: %CommonProgramFiles(x86)%\SSL
109
110For VC-WIN64, the following defaults are use:
111
112 PREFIX: %ProgramW6432%\OpenSSL
113 OPENSSLDIR: %CommonProgramW6432%\SSL
114
115Should those environment variables not exist (on a pure Win32
116installation for examples), these fallbacks are used:
117
118 PREFIX: %ProgramFiles%\OpenSSL
119 OPENSSLDIR: %CommonProgramFiles%\SSL
120
121ALSO NOTE that those directories are usually write protected, even if
122your account is in the Administrators group. To work around that,
123start the command prompt by right-clicking on it and choosing "Run as
124Administrator" before running `nmake install`. The other solution
125is, of course, to choose a different set of directories by using
126`--prefix` and `--openssldir` when configuring.
127
128Special notes for Universal Windows Platform builds, aka `VC-*-UWP`
129-------------------------------------------------------------------
130
131 - UWP targets only support building the static and dynamic libraries.
132
133 - You should define the platform type to `uwp` and the target arch via
134 `vcvarsall.bat` before you compile. For example, if you want to build
135 `arm64` builds, you should run `vcvarsall.bat x86_arm64 uwp`.
136
137Native builds using Embarcadero C++Builder
138=========================================
139
140This toolchain (a descendant of Turbo/Borland C++) is an alternative to MSVC.
141OpenSSL currently includes an experimental 32-bit configuration targeting the
142Clang-based compiler (`bcc32c.exe`) in v10.3.3 Community Edition.
143<https://www.embarcadero.com/products/cbuilder/starter>
144
145 1. Install Perl.
146
147 2. Open the RAD Studio Command Prompt.
148
149 3. Go to the root of the OpenSSL source directory and run:
150 `perl Configure BC-32 --prefix=%CD%`
151
152 4. `make -N`
153
154 5. `make -N test`
155
156 6. Build your program against this OpenSSL:
157 * Set your include search path to the "include" subdirectory of OpenSSL.
158 * Set your library search path to the OpenSSL source directory.
159
160Note that this is very experimental. Support for 64-bit and other Configure
161options is still pending.
162
163Native builds using MinGW
164=========================
165
166MinGW offers an alternative way to build native OpenSSL, by cross compilation.
167
168 * Usually the build is done on Windows in a GNU-like environment called MSYS2.
169
170 MSYS2 provides GNU tools, a Unix-like command prompt,
171 and a UNIX compatibility layer for applications.
172 However, in this context it is only used for building OpenSSL.
173 The resulting OpenSSL does not rely on MSYS2 to run and is fully native.
174
175 Requirement details
176
177 - MSYS2 shell, from <https://www.msys2.org/>
178
179 - Perl, at least version 5.10.0, which usually comes pre-installed with MSYS2
180
181 - make, installed using `pacman -S make` into the MSYS2 environment
182
183 - MinGW[64] compiler: `mingw-w64-i686-gcc` and/or `mingw-w64-x86_64-gcc`.
184 These compilers must be on your MSYS2 $PATH.
185 A common error is to not have these on your $PATH.
186 The MSYS2 version of gcc will not work correctly here.
187
188 In the MSYS2 shell do the configuration depending on the target architecture:
189
190 ./Configure mingw ...
191
192 or
193
194 ./Configure mingw64 ...
195
196 or
197
198 ./Configure ...
199
200 for the default architecture.
201
202 Apart from that, follow the Unix / Linux instructions in `INSTALL.md`.
203
204 * It is also possible to build mingw[64] on Linux or Cygwin.
205
206 In this case configure with the corresponding `--cross-compile-prefix=`
207 option. For example
208
209 ./Configure mingw --cross-compile-prefix=i686-w64-mingw32- ...
210
211 or
212
213 ./Configure mingw64 --cross-compile-prefix=x86_64-w64-mingw32- ...
214
215 This requires that you've installed the necessary add-on packages for
216 mingw[64] cross compilation.
217
218Linking native applications
219===========================
220
221This section applies to all native builds.
222
223If you link with static OpenSSL libraries, then you're expected to
224additionally link your application with `WS2_32.LIB`, `GDI32.LIB`,
225`ADVAPI32.LIB`, `CRYPT32.LIB` and `USER32.LIB`. Those developing
226non-interactive service applications might feel concerned about
227linking with `GDI32.LIB` and `USER32.LIB`, as they are justly associated
228with interactive desktop, which is not available to service
229processes. The toolkit is designed to detect in which context it's
230currently executed, GUI, console app or service, and act accordingly,
231namely whether to actually make GUI calls. Additionally, those
232who wish to `/DELAYLOAD:GDI32.DLL` and `/DELAYLOAD:USER32.DLL` and
233actually keep them off service process should consider implementing
234and exporting from .exe image in question own `_OPENSSL_isservice` not
235relying on `USER32.DLL`. E.g., on Windows Vista and later you could:
236
237 __declspec(dllexport) __cdecl BOOL _OPENSSL_isservice(void)
238 {
239 DWORD sess;
240
241 if (ProcessIdToSessionId(GetCurrentProcessId(), &sess))
242 return sess == 0;
243 return FALSE;
244 }
245
246If you link with OpenSSL .DLLs, then you're expected to include into
247your application code a small "shim" snippet, which provides
248the glue between the OpenSSL BIO layer and your compiler run-time.
249See also the OPENSSL_Applink manual page.
250
251Hosted builds using Cygwin
252==========================
253
254Cygwin implements a POSIX/Unix runtime system (`cygwin1.dll`) on top of the
255Windows subsystem and provides a Bash shell and GNU tools environment.
256Consequently, a build of OpenSSL with Cygwin is virtually identical to the
257Unix procedure.
258
259To build OpenSSL using Cygwin, you need to:
260
261 * Install Cygwin, see <https://cygwin.com/>
262
263 * Install Cygwin Perl, at least version 5.10.0
264 and ensure it is in the $PATH
265
266 * Run the Cygwin Bash shell
267
268Apart from that, follow the Unix / Linux instructions in INSTALL.md.
269
270NOTE: `make test` and normal file operations may fail in directories
271mounted as text (i.e. `mount -t c:\somewhere /home`) due to Cygwin
272stripping of carriage returns. To avoid this, ensure that a binary
273mount is used, e.g. `mount -b c:\somewhere /home`.
注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette