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.
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 | 2 years ago | |
build-android | 2 years ago | |
build-windows | 2 years ago | |
scripts | 2 years ago | |
src | 2 years ago | |
test | 2 years ago | |
.clang-format | 2 years ago | |
.gitignore | 2 years ago | |
.gitlab-ci.yml | 2 years ago | |
DEPENDENCIES | 2 years ago | |
LICENSE.txt | 5 years ago | |
Makefile | 2 years ago | |
Makefile.conf | 2 years ago | |
README.md | 2 years ago | |
local.conf.example | 3 years ago |
README.md
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:
PREFIX=$(HOME)/code/libad/build
ENGINE_LIB=-L$(HOME)/code/engine/build/lib
ENGINE_INC=-I$(HOME)/code/engine/build/include
Now, run:
make all
make install