libSBOL
2.3.3
|
Although it is generally advised to build libraries from source, we offer few different ways to obtain libSBOL.
For help configuring a client project, see Creating a Visual Studio project on Windows or Creating an XCode project on Mac OSX.
On Windows, installation through binary installers is the simplest way to obtain libSBOL. The installer contains pre-compiled libSBOL library. Simply install it to whichever path you want and use it.
Get the latest binary installers
On MacOSX, installation via the Homebrew package manager is easiest. Install libSBOL by running the following command in terminal:
To build libSBOL from source, you will need:
All the development has been done using "default native compilers" and Visual Studio on Windows or Unix makefiles on Mac/Linux. CMake can be used to generate projects for Eclipse, MinGW, XCode, etc.
For more details on running libSBOL on Mac, check Creating an XCode project on Mac OSX. For more details on running libSBOL on Windows using Visual Studio, check Creating a Visual Studio project on Windows.
Set optional targets, e.g. examples, tests, manual, or Python wrapper. To add them check the appropriate boxes and then press Configure again. It is HIGHLY RECOMMENDED to change CMAKE_INSTALL_PREFIX from it's default path (Program Files) to somewhere else. This value determines the path the output files will be located. Building Python wrapper requires SWIG.
SBOL_BUILD_SHARED: Builds a dynamically linked library. The default is static.
SBOL_BUILD_32: Build for 32-bit architectures
SBOL_BUILD_64: Build for 64-bit architectures.
SBOL_BUILD_PYTHON2: Build SWIG-Python wrappers for Python version 2
SBOL_BUILD_PYTHON3: Build SWIG-Python wrappers for Python version 3 (not reverse compatible)
If you want to try either 32 bit or 64 bit version of libSBOL, make sure you are using the right type of compiler. (Visual Studio 14 2015 vs Visual Studio 14 2015 Win64). For Python bindings, you need SWIG and Python libraries. CMake will try to look it up for you, but if it cannot, specify the path manually.
Set optional targets, e.g. examples, tests, manual, or Python wrapper. To add them check the appropriate boxes and then press Configure again. CMAKE_INSTALL_PREFIX is of particular interest, since it determines the path the output will be located. By default on Mac OSX, the library will be installed to /usr/local/lib. Building Python wrapper requires SWIG.
SBOL_BUILD_SHARED: Builds a dynamically linked library. The default is static.
SBOL_BUILD_32: Build for 32-bit architectures.
SBOL_BUILD_64: Build for 64-bit architectures.
SBOL_BUILD_PYTHON2: Build SWIG-Python wrappers for Python version 2
SBOL_BUILD_PYTHON3: Build SWIG-Python wrappers for Python version 3 (not reverse compatible)
For Python bindings, you need SWIG and Python libraries. CMake will try to look it up for you, but if it cannot, specify the path manually.
Set optional targets, e.g. examples, tests, manual, or Python wrapper. To add them check the appropriate boxes and then press Configure again. CMAKE_INSTALL_PREFIX is of particular interest, since it determines the path the output will be located. Building Python wrapper requires SWIG.
SBOL_BUILD_SHARED: Builds a dynamically linked library. The default is static.
SBOL_BUILD_32: Build for 32-bit architectures.
SBOL_BUILD_64: Build for 64-bit architectures.
SBOL_BUILD_PYTHON2: Build SWIG-Python wrappers for Python version 2
SBOL_BUILD_PYTHON3: Build SWIG-Python wrappers for Python version 3 (not reverse compatible)
For Python bindings, you need SWIG and Python libraries. CMake will try to look it up for you, but if it cannot, specify the path manually. If you want to build against Python 3.5, you will need to install it in you local machine first. To install run:
LibSBOL depends on libxml2 and raptor2 libraries for I/O in XML and RDF formats. Windows releases include precompiled binaries for these dependencies libSBOL. On Mac, these libraries are typically installed by default.
Optionally, LibSBOL depends on libCurl and Jsoncpp for web integration. This is useful for features like querying biological parts in a repository or validating SBOL files. This dependency is managed by Git's submodule feature. After cloning the libSBOL project, you can clone the submodules if you wish to build it along with libSBOL:
A .gitmodules configuration file is included in the project root.