VirtualBox

Changes between Version 65 and Version 66 of Mac OS X build instructions


Ignore:
Timestamp:
Aug 31, 2011 6:39:55 PM (13 years ago)
Author:
Christian Pötzsch
Comment:

small updates

Legend:

Unmodified
Added
Removed
Modified
  • Mac OS X build instructions

    v65 v66  
    33== Prerequisites on Mac OS X ==
    44
    5  * Mac OS X 10.4.x (Tiger), 10.5.x (Leopard), 10.6.x (Snow Leopard) or 10.7 (Lion) running on Intel hardware (PowerPC hardware is '''not''' supported). Please note that Tiger support was dropped with the 3.1 release.
     5 * Mac OS X 10.4.x (Tiger), 10.5.x (Leopard), 10.6.x (Snow Leopard) or 10.7.x (Lion) running on Intel hardware (PowerPC hardware is '''not''' supported). Please note that Tiger support was dropped with the 3.1 release.
    66
    77 * Xcode matching your Mac OS X version (http://developer.apple.com/tools/download/):
     
    1212
    1313 * Some things from !MacPorts (http://www.macports.org/). [[BR]]
    14  After installing !MacPorts, do not forget to add the following two lines to your ~/.profile
     14 After installing !MacPorts, do not forget to add the following two lines to your `~/.profile`
    1515{{{
    1616export PATH=/opt/local/bin:/opt/local/sbin:$PATH
     
    3636 * Qt/Mac (http://qt.nokia.com/downloads/qt-for-open-source-cpp-development-on-mac-os-x) [[BR]]
    3737 Carbon 4.4.x upwards for Tiger[[BR]]
    38  Cocoa 4.5.x upwards for Leopard/Snow Leopard[[BR]]
     38 Cocoa 4.5.x upwards for Leopard/Snow Leopard/Lion[[BR]]
    3939
    4040 * LaTeX ("sudo port install texlive texlive-fonts-extra texlive-latex-extra texlive-latex-recommended") for building the documentation
     
    4646./configure --disable-hardening
    4747}}}
    48  You can manually set the target architecture with --target-arch=x86 or amd64, if some architecture related problems occur.
     48 You can manually set the target architecture with `--target-arch=x86` or `amd64`, if some architecture related problems occur.
    4949
    50  If it finds everything it needs, it will create a file called '!AutoConfig.kmk' containing paths to the various tools on your system. Also, it will create an environment setup script called env.sh. This step only has to be done once (if something changes in your build tool setup, you might have to repeat it but keep in mind that both output files will be overwritten). For additional options like providing a path to the OpenSSL library see './configure --help'.
    51  2. Whenever you want to build !VirtualBox, you have to open a shell and source the generated environment setup script 'env.sh', i.e. do
     50 If it finds everything it needs, it will create a file called `!AutoConfig.kmk` containing paths to the various tools on your system. Also, it will create an environment setup script called env.sh. This step only has to be done once (if something changes in your build tool setup, you might have to repeat it but keep in mind that both output files will be overwritten). For additional options like providing a path to the OpenSSL library see `./configure --help`.
     51 2. Whenever you want to build !VirtualBox, you have to open a shell and source the generated environment setup script `env.sh`, i.e. do
    5252{{{
    5353. ./env.sh
     
    5858kmk
    5959}}}
    60     The default is to a release build, should you wish to do a ''debug'' or ''profile'' build add {{{BUILD_TYPE=debug}}} or {{{BUILD_TYPE=profile}}} as argument to ''kmk'' or export it as an environment variable in your shell.
     60    The default is to a release build, should you wish to do a ''debug'' or ''profile'' build add {{{BUILD_TYPE=debug}}} or {{{BUILD_TYPE=profile}}} as argument to `kmk` or export it as an environment variable in your shell.
    6161
    6262=== Tips for building !VirtualBox on Snow Leopard 32bit ===
     
    6464For backward compatibility (that is Leopard) !VirtualBox is build against the 10.5 SDK even on Snow Leopard (32bit). This can be problematic if you are using e.g. OpenSSL from !MacPorts which is build against the 10.6 SDK. You have two possibilities to solve this problem:
    6565
    66  1. Build all dependencies yourself and point them to the 10.5 SDK. Use e.g. ./configure --with-openssl-dir=/path/to/self/build/OpenSSL' before building !VirtualBox.
     66 1. Build all dependencies yourself and point them to the 10.5 SDK. Use e.g. `./configure --with-openssl-dir=/path/to/self/build/OpenSSL` before building !VirtualBox.
    6767
    68  2. If you don't care about backwards compatibility, you can force !VirtualBox to be build against the 10.6 SDK. For this include the following into a file called !LocalConfig.kmk, which should be located in the top level directory of the !VirtualBox build tree:
     68 2. If you don't care about backwards compatibility, you can force !VirtualBox to be build against the 10.6 SDK. For this include the following into a file called `LocalConfig.kmk`, which should be located in the top level directory of the !VirtualBox build tree:
    6969{{{
    7070VBOX_DEF_MACOSX_VERSION_MIN = 10.6

© 2023 Oracle
ContactPrivacy policyTerms of Use