Depends on #16, #31
We have to start using package manager (in our case - Conan).
To make our first Conan example, let's separate net-core package and http package, AND install our own Conan server (probably somewhere on cloud - TBD; later we'll try pushing our stuff to conan-center).
For the end-user (developer), the whole thing should look as follows:
- configure conan to use our Conan server
- "conan install nodecpp.net-core"; should install everything, including net-core as a lib, and binaries for static checker. NB: net-core lib should include files from logging and clustering folders
When adding a new package http (or any other package for that matter):
- "conan install nodecpp.http"
- add "permitted APIs" file from nodecpp.http to her own list of the allowed APIs (for static checker)
- #include "some_folder/http.h"
That's it - she can start coding using APIs provided by the http package.
with all Conan recipes, we have to support the following:
- platforms/configs:
- Windows/Visual Studio 19: x86_64, Debug (using MTd) / Release (using MT)
- Linux/clang 9: x86_64, Debug (using -g) / Release (using -O3 -DNDEBUG)
- options (implemented via #defines): unsafe, cluster
Depends on #16, #31
We have to start using package manager (in our case - Conan).
To make our first Conan example, let's separate net-core package and http package, AND install our own Conan server (probably somewhere on cloud - TBD; later we'll try pushing our stuff to conan-center).
For the end-user (developer), the whole thing should look as follows:
When adding a new package http (or any other package for that matter):
That's it - she can start coding using APIs provided by the http package.
with all Conan recipes, we have to support the following: