Is your Mac up to date with the latest version of the Mac operating system? Is it using the version required by a product that you want to use with your Mac? Which versions are earlier (older) or later (newer, more recent)? To find out, learn which version is installed now.
If your macOS isn't up to date, you may be able to update to a later version.
BoostSelect is classified as adware that serves various intrusive advertisements during the web browsing session. Also, it has browser hijacking apps’ feature to promote a fake search engine by modifying the settings of installed browsers, as well. It promotes Safe Finder through akamaidhd.net.
From the Apple menu  in the corner of your screen, choose About This Mac. You should see the macOS name, such as macOS Big Sur, followed by its version number. If you need to know the build number as well, click the version number to see it.
These are all Mac operating systems, starting with the most recent. When a major new macOS is released, it gets a new name, such as macOS Big Sur. As updates that change the macOS version number become available, this article is updated to show the latest version of that macOS.
If your Mac is using an earlier version of any Mac operating system, you should install the latest Apple software updates, which can include important security updates and updates for the apps that are installed by macOS, such as Safari, Books, Messages, Mail, Music, Calendar, and Photos.
macOS | Latest version |
---|---|
macOS Big Sur | 11.3 |
macOS Catalina | 10.15.7 |
macOS Mojave | 10.14.6 |
macOS High Sierra | 10.13.6 |
macOS Sierra | 10.12.6 |
OS X El Capitan | 10.11.6 |
OS X Yosemite | 10.10.5 |
OS X Mavericks | 10.9.5 |
OS X Mountain Lion | 10.8.5 |
OS X Lion | 10.7.5 |
Mac OS X Snow Leopard | 10.6.8 |
Mac OS X Leopard | 10.5.8 |
Mac OS X Tiger | 10.4.11 |
Mac OS X Panther | 10.3.9 |
Mac OS X Jaguar | 10.2.8 |
Mac OS X Puma | 10.1.5 |
Mac OS X Cheetah | 10.0.4 |
This section provides some guidelines on how to install and configure BoostBook and Quickbook under several operating systems. Before installing you'll need a local copy of boost, and to install the version of bjam
which comes with it (or a later version).
The simplest way to install on OS X is to use macports. If you don't want to use macports and are using Snow Leopard or later, there are instructions later. Earlier versions of OS X need to use something like macports to install xsltproc
because the version they come with is very old, and doesn't have good enough XSL support for boostbook's stylesheets.
First install the libxslt
, docbook-xsl
and docbook-xml-4.2
packages:
Next, we need to configure Boost Build to compile BoostBook files. Add the following to your user-config.jam
file, which should be in your home directory. If you don't have one, create a file containing this text. For more information on setting up user-config.jam
, see the Boost Build documentation.
The above steps are enough to get a functional BoostBook setup. Quickbook will be automatically built when needed. If you want to avoid these rebuilds:
BOOST_ROOT/tools/quickbook
). bjam
. quickbook
binary (located at BOOST_ROOT/dist/bin
) to a safe place. The traditional location is /usr/local/bin
. Add the following to your user-config.jam
file, using the full path of the quickbook executable:
If you need to build documentation that uses Doxygen, you will need to install it as well:
And then add to your user-config.jam
:
Alternatively, you can install from the official doxygen dmg
. This is described at the end of the next section.
Section contributed by Julio M. Merino Vidal
The text below assumes you want to install all the necessary utilities in a system-wide location, allowing any user in the machine to have access to them. Therefore, all files will be put in the /usr/local
hierarchy. If you do not want this, you can choose any other prefix such as ~/Applications
for a single-user installation.
Snow Leopard comes with xsltproc
and all related libraries preinstalled, so you do not need to take any extra steps to set them up. It is probable that future versions will include them too, but these instructions may not apply to older versions.
To get started:
/usr/local/share/xml/docbook/4.2
. docbook-xsl-1.nn.n.tar.bz2
, with no suffix such as -ns.tar.bz2
or -doc.tar.bz2
. Put the results in /usr/local/share/xsl/docbook
, thus effectively removing the version number from the directory name (for simplicity). Add the following to your user-config.jam
file, which should live in your home directory (/Users/<your_username>
). You must already have it somewhere or otherwise you could not be building Boost (i.e. missing tools configuration).
The above steps are enough to get a functional BoostBook setup. Quickbook will be automatically built when needed. If you want to avoid these rebuilds and install a system-wide Quickbook instead:
BOOST_ROOT/tools/quickbook
). bjam
. quickbook
binary (located at BOOST_ROOT/dist/bin
) to a safe place. Following our previous example, you can install it into: /usr/local/bin
. Add the following to your user-config.jam
file:
Additionally, if you need to build documentation that uses Doxygen, you will need to install it too:
dmg
file) for Mac OS X. Applications
folder to install it. Add the following to your user-config.jam
file:
Section contributed by Julio M. Merino Vidal
The following instructions apply to any Windows system based on Windows 2000, including Windows XP, Windows 2003 Server, Windows Vista, and Windows 7. The paths shown below are taken from a Windows Vista machine; you will need to adjust them to match your system in case you are running an older version.
xsltproc
for Windows. There are many ways to get this tool, but to keep things simple, use the binary packages made by Igor Zlatkovic. At the very least, you need to download the following packages: iconv
, zlib
, libxml2
and libxslt
. bin
, include
and lib
directories within the hierarchy. These instructions use C:UsersexampleDocumentsboostxml
as the root for all files. bin
directory and launch xsltproc.exe
to ensure it works. You should get usage information on screen. C:UsersexampleDocumentsboostxmldocbook-xml
. docbook-xsl-1.nn.n.tar.bz2
, with no suffix such as -ns.tar.bz2
or -doc.tar.bz2
. To make things easier, rename the directory created during the extraction to docbook-xsl
(bypassing the version name): C:UsersexampleDocumentsboostxmldocbook-xsl
. Add the following to your user-config.jam
file, which should live in your home directory (%HOMEDRIVE%%HOMEPATH%
). You must already have it somewhere or otherwise you could not be building Boost (i.e. missing tools configuration).
The above steps are enough to get a functional BoostBook setup. Quickbook will be automatically built when needed. If you want to avoid these rebuilds:
BOOST_ROOTtoolsquickbook
). bjam
. quickbook.exe
binary (located at BOOST_ROOTdistbin
) to a safe place. Following our previous example, you can install it into: C:UsersexampleDocumentsboostxmlbin
. Add the following to your user-config.jam
file:
The following instructions apply to Debian and its derivatives. They are based on a Ubuntu Edgy install but should work on other Debian based systems. They assume you've already installed an appropriate version of bjam
for your copy of boost.
First install the xsltproc
, docbook-xsl
and docbook-xml
packages. For example, using apt-get
:
If you're planning on building boost's documentation, you'll also need to install the doxygen
package as well.
Next, we need to configure Boost Build to compile BoostBook files. Add the following to your user-config.jam
file, which should be in your home directory. If you don't have one, create a file containing this text. For more information on setting up user-config.jam
, see the Boost Build documentation.
The above steps are enough to get a functional BoostBook setup. Quickbook will be automatically built when needed. If you want to avoid these rebuilds:
BOOST_ROOT/tools/quickbook
). bjam
. quickbook
binary (located at BOOST_ROOT/dist/bin
) to a safe place. The traditional location is /usr/local/bin
. Add the following to your user-config.jam
file, using the full path of the quickbook executable: