LMDB Abstraction Layer. A library to ease interactions with LMDB
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Blue 4975721a5c
0.3.1 fix qt5 build, exception docs
2 months ago
cmake cmake magick to make package usable and discoverable by another CMake projects, readme, pkgbuild 2 months ago
doc Base class documentation, doxugen tweaking, new exception for one case 2 months ago
packaging/Archlinux 0.3.1 fix qt5 build, exception docs 2 months ago
src 0.3.1 fix qt5 build, exception docs 2 months ago
test one more test for adding multiple entries, fix of leaking cursor, Storage::change method rework, beginning of documentation 2 months ago
CHANGELOG.md 0.3.1 fix qt5 build, exception docs 2 months ago
CMakeLists.txt 0.3.1 fix qt5 build, exception docs 2 months ago
LICENSE.md licensing, initial documentation initiative 2 months ago
README.md 0.3.0 2 months ago


LMDBAL - Lightning Memory Data Base Abstraction Level

AUR license AUR version Liberapay patrons Documentation


  • Qt 5 or higher
  • lmdb
  • CMake 3.16 or higher
  • Doxygen (optional, for documentation)

Using with CMake

As a system library

If you're using LMDBAL as a system library you probably have no control over it's build options. The easiest way to include the project is to add following

    target_include_directories(yourTarget PRIVATE ${LMDBAL_INCLUDE_DIRS})
    target_link_libraries(yourTarget PRIVATE LMDBAL::LMDBAL)

As an embeded subproject

If you're using LMDBAL as a embeded library you might want to control it's build options, for example you can run


before including the library in your project. This will set the library to be build in a static mode.

Then you want to run something like this


target_link_libraries(yourTarget PRIVATE LMDBAL::LMDBAL)

The headers are added as PUBLIC so you might not even need to target_link_libraries them


LMDBAL uses CMake as a build system.

Please check the prerequisites and install them before building.

Here is an easy way to build a project

$ git clone https://git.macaw.me/blue/lmdbal
$ cd lmdbal
$ mkdir build
$ cd build
$ cmake .. [ *optional keys* ]
$ cmake --build .
$ cmake --install . --prefix install

This way will create you a lmdbal/build directory with temporary files, and lmdbal/build/install with all the export files for installation to the system.

After cmake .. you can specify keys to alter the building process. In this context building keys are transfered like so

cmake .. -D KEY1=VALUE1 -D KEY2=VALUE2 ...

List of keys

Here is the list of keys you can pass to configuration phase of cmake ..:

  • CMAKE_BUILD_TYPE - Debug just builds showing all warnings, Release builds with no warnings and applies optimizations (default is Debug);
  • BUILD_STATIC - True builds project as a static library, False builds as dynamic (default is False);
  • BUILD_TESTS - True build unit tests, False does not (default is False);
  • BUILD_DOC - True build doxygen documentation, False does not (default is False);
  • BUILD_DOXYGEN_AWESOME - True build doxygen awesome theme if BUILD_DOC is also True (default is False);
  • QT_VERSION_MAJOR - 5 links against Qt5, 6 links agains Qt6, there is no default, so, if you didn't specify it the project will chose automatically;

Running tests

If you built the library with -D BUILD_TESTS=True, then there will be lmdbal/build/tests/runUnitTests executable file. You can simply run it as


if you're in the same directory with it


This project is licensed under the GPLv3 License - see the LICENSE.md file for details