C++11 library providing functionality common to all adapters.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
heck ca0d30c175 Merge branch 'LIB-13' - Define Coding Standards And Project Structure
Define and implement Coding Style using clang-format.
top level .clang-format, supported by nearly all Editors/IDE's and if not, one has to manually run clang-format. Its up to the dev. But everybody can use it, and its enables to use a shared definition of coding style.

I want to avoid the project to end up in an underspecified/inconsistent state after the code base has grown over the years.
So, NOW is the time to do it.

Flat project structure becomes unmanageable.
Create standard project layout, of at least
* src
* test

for now

ALSO: The max. C++ Standard to be used (pEp-wide) has now been raised to C++14 (!!!)
2 years ago
.gitlab-ci-files CID: don't use insecure docker registries anymore 2 years ago
build-android Android Build: Add all *.cc source files instead of one by one 2 years ago
build-windows Add pEpLog to Visual Studio project 2 years ago
scripts CI: use specific project versions 2 years ago
src LIB-13: Standard project layout (src dir added) 2 years ago
test LIB-13: Standard project layout (src dir added) 2 years ago
.clang-format LIB-13: Add Carefully crafted .clang-format 2 years ago
.gitignore .gitignore 2 years ago
.gitlab-ci.yml CI: remove unfinished CentOS/RHEL jobs 2 years ago
DEPENDENCIES BUILD: use pEpEngine=Release_2.1.23 2 years ago
LICENSE.txt adding licensing and locked_queue 5 years ago
Makefile LIB-13: Standard project layout (src dir added) 2 years ago
Makefile.conf LIB-13: Standard project layout (src dir added) 2 years ago
README.md LIB-13: "Define Coding Standards And Project Structure" - Reformat (almost) the whole codebase using clang-format. 2 years ago
local.conf.example Unified local.conf with pEpJNIAdapter, added local.conf.example, (BUILD_CONFIG gone seemed to be broken, anyone missing it? /q heck) 3 years ago


How to build

To customize your build, you may change several variables that are consumed by make.

These variables, along with some explanations can be found in Makefile.conf.

You can edit that file, or create a file local.conf in the root of the repository, which will also be parsed by make.

A sample local.conf looks like this:



Now, run:

make all
make install