You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The generated flatbuffer header expects the flatbuffer headers to be located in a flatbuffers folder:
#include "flatbuffers/flatbuffers.h"
This is problematic when cross-building for embedded targets using the host installation of flatbuffers. The includes are located under /usr/include/flatbuffers in most Linux distributions. The generated flatbuffer header and also flatbuffers/flatbuffers.h require the compiler include path set to /usr/include which takes precedence over default compiler include paths. Various problems arise, like the compiler finding the wrong standard lib and so on.
There are ways to work around that problem like creating symlinks to /usr/include/flatbuffers somewhere in the project or build directory so that the compiler include path can be set to the folder containing the symlink. But that is neither portable nor maintainable.
I would prefer the flatbuffer headers if the flatbuffer did not require a flatbuffers include prefix at all or at least, if it would be configurable in the generated header.
The text was updated successfully, but these errors were encountered:
The generated flatbuffer header expects the flatbuffer headers to be located in a
flatbuffers
folder:This is problematic when cross-building for embedded targets using the host installation of flatbuffers. The includes are located under
/usr/include/flatbuffers
in most Linux distributions. The generated flatbuffer header and alsoflatbuffers/flatbuffers.h
require the compiler include path set to/usr/include
which takes precedence over default compiler include paths. Various problems arise, like the compiler finding the wrong standard lib and so on.There are ways to work around that problem like creating symlinks to
/usr/include/flatbuffers
somewhere in the project or build directory so that the compiler include path can be set to the folder containing the symlink. But that is neither portable nor maintainable.I would prefer the flatbuffer headers if the flatbuffer did not require a
flatbuffers
include prefix at all or at least, if it would be configurable in the generated header.The text was updated successfully, but these errors were encountered: