From 9bbf09b5c4597d05753b96d39580964ff5bca6ec Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=9B=D0=B5=D0=BE=D0=BD=D0=B8=D0=B4=20=D0=AE=D1=80=D1=8C?= =?UTF-8?q?=D0=B5=D0=B2=20=28Leonid=20Yuriev=29?= Date: Sat, 9 Jul 2022 14:54:25 +0300 Subject: [PATCH] mdbx: minor update README for the locations of a source code. --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index c4892b9b..3f78a26b 100644 --- a/README.md +++ b/README.md @@ -394,20 +394,20 @@ since release the version 1.0. _libmdbx_ provides two official ways for integration in source code form: -1. Using the amalgamated source code. - > The amalgamated source code includes all files required to build and +1. Using an amalgamated source code which available in the [releases section](https://gitflic.ru/project/erthink/libmdbx/release) on GitFlic. + > An amalgamated source code includes all files required to build and > use _libmdbx_, but not for testing _libmdbx_ itself. + > Beside the releases an amalgamated sources could be created any time from the original clone of git + > repository on Linux by executing `make dist`. As a result, the desired + > set of files will be formed in the `dist` subdirectory. -2. Adding the complete original source code as a `git submodule`. +2. Adding the complete source code as a `git submodule` from the [origin git repository](https://gitflic.ru/project/erthink/libmdbx) on GitFlic. > This allows you to build as _libmdbx_ and testing tool. > On the other hand, this way requires you to pull git tags, and use C++11 compiler for test tool. _**Please, avoid using any other techniques.**_ Otherwise, at least don't ask for support and don't name such chimeras `libmdbx`. -The amalgamated source code could be created from the original clone of git -repository on Linux by executing `make dist`. As a result, the desired -set of files will be formed in the `dist` subdirectory. ## Building and Testing