Changeset 6700 in vbox for trunk/src/VBox/Additions

Timestamp:

Jan 31, 2008 11:11:53 PM (17 years ago)

Author:

vboxsync

Message:

Updated the docs.

File:

• trunk/src/VBox/Additions/Makefile.kmk (modified) (1 diff)

trunk/src/VBox/Additions/Makefile.kmk

@@ -3 +3 @@
 # Top-level makefile for the VirtualBox Guest Additions.
 #
-# This makefile and all it's sub-makefiles are involved in remote
-# building of additions that cannot be build locally. Typically
-# tools/env.sh kmk -C src/VBox/Additions build-somehost-additions
-# is send as a command and the source tree is accessed using an
-# SMB mount.
+# Cross building of the additions is generally done by remote building
+# by means of smbfs, cifs, VBOX_ONLY_ADDITIONS=1 and setting BUILD_TARGET
+# to the desired target.
 #
-# When doing these operations BUILD_TARGET remains the same (not
-# yet true for linux), and it's therefore important that
-# Config.kmk and all the involved (sub-)makefiles doesn't make
-# assumptions about BUILD_TARGET being the same as the additions
-# target.
+# Limited support for cross building the windows additions using wine
+# is provided. There are a couple of issues with the approach (lack of
+# signing, no VC++ 8 support, ++) that makes it unsuitable for releases.
 #
-# To setup the remote building of an addition target, let's call it
-# XYZ, you need to add VBOX_REMOTE_XYZ_ADDITIONS_BUILD to your
-# LocalConfig.kmk. The value is the command(s) required to execute
-# the equivalent to you locally executing kmk -C src/VBoxAdditions
-# build_xyz_additions. This means BUILD_TARGET* and BUILD_TYPE needs
-# to be specified.
+# Building the linux additions as part of the l4 build is ok because
+# l4 is built on a linux platform. This is why we have to check if
+# BUILD_TARGET is l4 or linux in some places, though most of the magic
+# is done in the templates (Config.kmk).
 #