INSTALL 1.9 KB

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