Changes between Version 52 and Version 53 of Windows build instructions

Timestamp:

Jun 9, 2017 9:25:33 AM (7 years ago)

Author:

Frank Mehnert

Comment:

mention that external libraries need to be accessible from the output directory

Windows build instructions

@@ -161 +161 @@
 }}}
 
-which can be found in the output directory.  Note that for this to work, `VBoxSVC.exe` must not be running, so use the Windows task manager to verify this.  Usually `VBoxSVC.exe` terminates automatically after 5 seconds of inactivity (i.e. no client connection) but especially when developing, it might sometimes stay around.  In case the COM classes change (this usually happens when the file `VirtualBox.xidl` is updated) and you forget to re-register the classes, weird problems may appear.
+which can be found in the output directory (`out/win.ARCH/release/bin`).  Note that for this to work, `VBoxSVC.exe` must not be running, so use the Windows task manager to verify this.  Usually `VBoxSVC.exe` terminates automatically after 5 seconds of inactivity (i.e. no client connection) but especially when developing, it might sometimes stay around.  In case the COM classes change (this usually happens when the file `VirtualBox.xidl` is updated) and you forget to re-register the classes, weird problems may appear.
+
+Before you can start any binary from the output directory you have to make sure that external libraries (for example `libcurl.dll` or `libcrypto.dll`) are located in a directory which is accessible by the `PATH` variable or by copying these libraries to the output directory.
 
 In order to (re-)install the !VirtualBox kernel drivers, issue the following: