4 The build system used by luabind is Boost Build V2, which can be found
7 http://www.boost.org/doc/tools/build/index.html
9 The installation instructions are available at:
11 http://www.boost.org/doc/tools/build/doc/html/bbv2/installation.html
13 If you are using Debian or Ubuntu, you can simply install the
14 "boost-build" package:
16 $ sudo apt-get install boost-build
18 Other distributions may have similar packages.
20 On Windows, you can download pre-built "bjam" binaries, and follow the
21 installation instructions on the page linked above.
27 The environment variable "BOOST_ROOT" must be set to the directory where Boost
28 was extracted. "LUA_PATH" must be set to a directory where Lua binaries and
29 headers reside. The recommended way to get the Lua libraries is to download the
30 "DLL and Includes" package from:
32 http://luabinaries.luaforge.net/download.html
34 With these enviroment variables properly set:
40 Will build the default library variants and place them in a directory called
41 "stage". This can be controlled with the "--stagedir" option:
43 $ bjam --stagedir=libs stage
45 Would place the libraries in a "libs" directory.
47 Note that there is nothing magic going on here. If you don't want to
48 build the libraries this way, or run the tests, there is nothing
49 stopping you from using whatever build system you want. For example,
50 simply dropping the source files in a Visual Studio project should just
51 work. The only requirement is that "LUABIND_DYNAMIC_LINK" must be
52 defined when building and linking to a shared library.
59 Will build and install the default library variants, and install them together
60 with the header files to the default prefix, which is "/usr/local". The install
61 prefix can be controlled with the "--prefix" option. For example:
63 $ bjam --prefix=/usr install
65 Will install to "/usr/lib" and "/usr/include".