xlnt/docs/source/includes/_getting_started.md

2.6 KiB

Getting Started

Getting xlnt

Binaries

Homebrew

Arch

vcpkg

Compiling from Source

xlnt uses continous integration (thanks Travis CI and AppVeyor!) and passes all 270+ tests in GCC 4, GCC 5, VS2015 U3, and Clang (using Apple LLVM 8.0). Build configurations for Visual Studio 2015, GNU Make, and Xcode can be created using cmake v3.1+. A full list of cmake generators can be found here. A basic build would look like (starting in the root xlnt directory):

mkdir build
cd build
cmake ..
make -j8

The resulting shared (e.g. libxlnt.dylib) library would be found in the build/lib directory. Other cmake configuration options for xlnt can be found using "cmake -LH". These options include building a static library instead of shared and whether to build sample executables or not. An example of building a static library with an Xcode project:

mkdir build
cd build
cmake -D STATIC=ON -G Xcode ..
cmake --build .
cd bin && ./xlnt.test

Note for Windows: cmake defaults to building a 32-bit library project. To build a 64-bit library, use the Win64 generator

cmake -G "Visual Studio 14 2015 Win64" ..

Dependencies

xlnt requires the following libraries which are all distributed under permissive open source licenses. All libraries are included in the source tree as git submodules for convenience except for pole and partio's zip component which have been modified and reside in xlnt/source/detail:

Additionally, the xlnt test suite (bin/xlnt.test) requires an extra testing library. This test executable is separate from the main xlnt library assembly so the terms of this library's license should not apply to users of solely the xlnt library:

Initialize the submodules from the HEAD of their respective Git repositories with this command called from the xlnt root directory:

git submodule update --init --remote

Static vs. Dynamic