example-crud icon indicating copy to clipboard operation
example-crud copied to clipboard

Note regarding oatpp extensions installation instructions

Open Saadharta opened this issue 1 year ago • 0 comments

Hello there;

Here are my notes regarding oatpp extensions' installation, since i have had some difficulties with it. If the following happens to be of any interest to the OATPP mainainers, it can be used to enrich the project's documentation.

Note: the following commands use Release builds. My CMake version for some reasons isn't ejoying the -DCMAKE_BUILD_TYPE=Release option at config time so I used instead the --config Release option at build time

First, clone and build oatpp

$ cd <path/where/you/want/oatpp/repository/to/be/located>
$ git clone https://github.com/oatpp/oatpp.git
$ cd oatpp

# If needed, add -G and -A  options to the CMake configuration; cf CMake documentation :)
$ cmake -B build -S . -DOATPP_BUILD_TESTS=OFF

# Since i am on windows i then generated the library using Visual Studio.
# The regular build command yields the same result:
$ cmake --build build --config Release

Add OATPP_HOME to your path, pointing to <path/to/oatpp>. Althought not mandatory, it helps keeping the extension installation's command line understandable without <path/to/oatpp> everywhere.

then

$ cd <path/where/you/want/<oatpp-extension>/repository/to/be/located>
$ git clone https://github.com/oatpp/<oatpp-extension>.git
$ cd <oatpp-extension>

# Those shall point to oatpp source's folder and oatpp lib folder respectively
# Linux version:
$ cmake -B build -S . -DOATPP_MODULES_LOCATION=CUSTOM -DOATPP_DIR_SRC=$OATPP_HOME/src -DOATPP_DIRL_LIB=$OATPP_HOME/build/<path/to/lib/folder> -DOATPP_BUILD_TESTS=OFF

# Windows version:
# once again, if needed add -G and -A options
$ cmake -B build -S . -DOATPP_MODULES_LOCATION=CUSTOM -DOATPP_DIR_SRC=%OATPP_HOME%\\src -DOATPP_DIRL_LIB=%OATPP_HOME%\\build<path\\to\\lib\\folder> -DOATPP_BUILD_TESTS=OFF

cmake --build build --config Release

Now add <OATPP_EXTENSION>_HOME to your path, pointhing to <path/to/oatpp-extension>

You now have <oatpp> and <oatpp-extensions> libraries built.

Kind Regards,

Saadharta

Saadharta avatar Mar 31 '23 13:03 Saadharta