Feature #837
Von Maximilian Seesslen vor 13 Tagen aktualisiert
It is not an monolitic repository.
E.g. installing fosh library to an sysroot and compiling an application without cmake magic should still work.
The same configuration should be used which the library was compiled with.
Usecases:
* The library is included as subdirectory. The library detect that (Not-Top-Level) and use the generated header. Liblepto needed.
* The library is compiled at top level. Full-feature headers are used and installed. No generation.
* Install an whole project to an sysroot? Bad idea? E.g. build an CANIo without submodules.
Why using generated header at all?
Sources allways include <fosh/config.h>; either directly copied or generated.
Problem:
Man entwickelt an libfosh. Dort wird aber immer "fosh/config.h" aus der Sysroot herangezogen. Es muss in den CMake-Files so abgebildet sein,
dass wenn libfosh im projekt vohanden ist, auch immer nur die generierten header verwendet werden.
E.g. installing fosh library to an sysroot and compiling an application without cmake magic should still work.
The same configuration should be used which the library was compiled with.
Usecases:
* The library is included as subdirectory. The library detect that (Not-Top-Level) and use the generated header. Liblepto needed.
* The library is compiled at top level. Full-feature headers are used and installed. No generation.
* Install an whole project to an sysroot? Bad idea? E.g. build an CANIo without submodules.
Why using generated header at all?
Sources allways include <fosh/config.h>; either directly copied or generated.
Problem:
Man entwickelt an libfosh. Dort wird aber immer "fosh/config.h" aus der Sysroot herangezogen. Es muss in den CMake-Files so abgebildet sein,
dass wenn libfosh im projekt vohanden ist, auch immer nur die generierten header verwendet werden.