Daryle Walker wrote:
That include of file in "libs" will be made from .cpp file. After installation, that line will be already compiled to .obj, included in .so and the include will not be visible by the user.
So the #includes would be one file in "libs" including a sibling file in "libs," right?
Right.
Do you still have the objection?
Depends if compilers can easily be made to look for a source file's siblings. (Since source files are listed in projects/makefiles directly, their containing directories don't have to be in any search path.)
There will be an include with explicit path ("../../detail/utf8/utf8_codecvt.cpp"). If there's any compiler which does not consider "." for quoted includes, it's always possible to add "." to the search path. - Volodya