Context Navigation

Changes between Version 51 and Version 52 of Windows build instructions

Timestamp:: Jun 9, 2017 7:59:13 AM (7 years ago)
Author:: Frank Mehnert
Comment:: more updates

Legend:

: Unmodified
: Added
: Removed
: Modified

Windows build instructions

-              v51
+              v52
  * the '''libxml2''' library. Sources and 32bit binaries can be downloaded from: [[BR]]
  http://xmlsoft.org/downloads.html [[BR]]
- http://xmlsoft.org/XSLT/downloads.html [[BR]]
  ''Use `--with-libxml2=` to specify the path for configure.vbs.''
  * the '''zlib''' library. Grab the sources from: [[BR]]
  http://www.zlib.net/ [[BR]]
  Actually the tarball comes with zlib in the `src/libs/` directory already so downloading this library is only necessary if you need a new version. In that case look for `SDK_VBOX_ZLIB_INCS` and `SDK_VBOX_ZLIB_LIBS` in Config.kmk and override these entries in your LocalConfig.kmk (see below for some notes about LocalConfig.kmk).
+ Actually the tarball includes `zlib` in the `src/libs/` directory so downloading this library is only necessary if you need a more recent version. In that case look for `SDK_VBOX_ZLIB_INCS` and `SDK_VBOX_ZLIB_LIBS` in Config.kmk and override these entries in your {{{LocalConfig.kmk}}} accordingly. See [#LocalConfig below] for some notes about using {{{LocalConfig.kmk}}} to override the default build configuration).
  * the '''cURL''' library. Grab the binaries from: [[BR]]
 …
  Normally part of the WDK: `certmgr.exe`, `makecert.exe`, `signtool.exe` and so on.
  * ''Optional:'' '''NSIS 2.51''', only needed if you want to build the Guest Additions including the installer. Required plugins: NsSCM, AccessControl, NsProcess and nsisunz. Grab the sources or setup from: [[BR]]
+ * ''Optional:'' '''NSIS 2.51''', only needed if you want to build the Guest Additions including the installer. Required plugins: `NsSCM`, `AccessContro`, `NsProcess` and `nsisunz`. Grab the sources or setup from: [[BR]]
  https://sourceforge.net/projects/nsis/files/NSIS%202/2.51/
  * ''Optional:'' '''gSOAP 2.8.x''', only needed if you want to build the webservice API server. Grab the sources from: [[BR]]
  http://sourceforge.net/projects/gsoap2/files/gSOAP/gSOAP%202.7.12%20stable/ [[BR]]
+ Add `VBOX_PATH_GSOAP=/path/to/gsoap-VERSION/gsoap` and `VBOX_GSOAP_INSTALLED=1` to your LocalConfig.kmk file (no autodetection from configure.vbs).
+ Add `VBOX_PATH_GSOAP=/path/to/gsoap-VERSION/gsoap` and `VBOX_GSOAP_INSTALLED=1` to your {{{LocalConfig.kmk}}} file (no autodetection from configure.vbs).
  * ''Optional:'' '''Python 2.7.x''', only needed if you want to build Python API bindings, both webservice and COM. Grab the binaries from: [[BR]]
 …
 === Manual compilation of certain prerequisites ===
 If you don't find development packages of certain prerequisites it's also possible to manually compile them. For instance, there does not seem to be proper libcurl packages avaible for Windows which contain the .lib files, the .dll files as well as the `include/` directory.
+If you don't find development packages of certain prerequisites it's also possible to manually compile them. For instance, there does not seem to be proper `libcurl` packages avaible for Windows which contain `libcurl.lib`, `libcurl.dll' files and the `include/` directory.
 To manually build the cURL devel package on Windows you have to
 . Take care that the compiler binary path is part of the '''`PATH`''' environment variable, usually the `bin/` directory of the installation directory. That directory has to contain `cl.exe`, `link.exe`, `lib.exe`, `nmake.exe` etc. Take care to point to the correct architecture path (amd64 or x86).
+. Take care that the compiler binary path is part of the '''`PATH`''' environment variable, usually the `bin/` directory of the installation directory. That directory has to contain `cl.exe`, `link.exe`, `lib.exe`, `nmake.exe` etc. Take care to specify the correct architecture path (amd64 or x86).
 . Set the '''`INCLUDE`''' environment variable to include the compilers `atlmfc/include/` (ATL/MFC) and `include/` directories.
 . Set the '''`LIB`''' environment variable to include the compilers `atlmfc/lib/` (ATL/MFC) and `lib/` directories. Take care to point to the correct architecture path (amd64 or x86).
 . Set the '''`LIBPATH`''' environment variable to include the compilers `atlmfc/lib/` (ATL/MFC) directory. Take care to point to the correct architecture path (amd64 or x86).
+. Set the '''`LIB`''' environment variable to include the compilers `atlmfc/lib/` (ATL/MFC) and `lib/` directories. Take care to specify the correct architecture path (amd64 or x86).
+. Set the '''`LIBPATH`''' environment variable to include the compilers `atlmfc/lib/` (ATL/MFC) directory. Take care to specify the correct architecture path (amd64 or x86).
 . Set the '''`PATH`''' environment variable to include the (7.1) SDK `bin/` directory. Take care to point to the correct architecture path (amd64 or x86).
 . Set the '''`INCLUDE`''' environment variable to include the (7.1) SDK `include/` directory.
 . Set the '''`LIB`''' environment variable to include the (7.1) SDK `lib/` directory. Take care to point to the correct architecture path (amd64 or x86).
+. Set the '''`LIB`''' environment variable to include the (7.1) SDK `lib/` directory. Take care to specify the correct architecture path (amd64 or x86).
 After all these environment variables are set up, go to the `curl-VERSION/winbuild/` directory and perform
 {{{
 …
 nmake /f Makefile.vc mode=dll VC=10 MACHINE=x86
 }}}
 The resulting package can be found in `libcurl-vc10-*-winssl/` directory. The configure.vbs script expects that libcurl.lib and libcurl.dll are located next to the `include/` directory. It's a good idea to copy the `libcurl-vc10-*-winssl/` directory to another place. Then use the `--with-libcurl=` parameter to tell configure.vbs the path.
+The resulting package can be found in the `libcurl-vc10-*-winssl/` directory. The configure.vbs script expects that libcurl.lib and libcurl.dll are located next to the `include/` directory. It's a good idea to copy the `libcurl-vc10-*-winssl/` directory to another place. Then use the `--with-libcurl=` parameter to specify the path for configure.vbs.
 == Building !VirtualBox ==
 …
 . Change to the root directory of the sources and enter our build shell environment: `env.bat`.
 . To manually override any tool or change Config.kmk settings, create LocalConfig.kmk in the root directory of the sources and place the setting there. For instance, to create a non-hardened build ('''only for testing'''), add `VBOX_WITHOUT_HARDENING = 1` to LocalConfig.kmk.
+. To manually override any tool or change Config.kmk settings, create {{{LocalConfig.kmk}}} in the root directory of the sources and place the setting there. See [#LocalConfig below] for an incomplete of possible settings.
 . To build a release package, type `kmk`. This produces the binaries in `out\win.x86\release\bin`. If you want to build a debug version, enter `kmk KBUILD_TYPE=debug`.
+. To build a release package, type `kmk`. This produces the binaries in `out\win.x86\release\bin` (or `out\win.amd64\release\bin` on 64-bit hosts). If you want to build a debug version, enter `kmk KBUILD_TYPE=debug`.
+. To create an `.msi` package, type `kmk packing'.
 === Using Visual C++ 2010 Express ===
 …
 cscript configure.vbs --with-VC-Express-Edition
 }}}
+=== Excluding certain features from building === #LocalConfig
+Here is an incomplete list of settings which could be added to {{{LocalConfig.kmk}}}:
+ VBOX_WITH_ADDITIONS=::
+  Don't build the !VirtualBox Guest Additions.
+ VBOX_ONLY_ADDITIONS=1::
+  Build the Guest Additions exclusively.
+ VBOX_WITH_VALIDATIONKIT=::
+  Don't build the !VirtualBVox validation kit.
+ VBOX_WITHOUT_HARDENING=1::
+  Disable Windows hardening. Useful for testing. Do '''not''' use this setting for production builds! Without hardening the binaries are not signed and !VirtualBox.exe can be started straight away from the out/.../bin directory (`kmk packing` + installation not required).
 === Only for 64 bit builds: setting up self signing ===