When fpl2cc is used outside its own source project, error messages from embedded headers have erroneous and/or misleading paths.
This shows up particularly if you try to compile the generated code using the default clang++ on OSX!
For example:
sunbird:rage chris$ clang++ src/rage.cc -o bin/rageIn file included from src/rage.cc:3:src/util/fs.h:10:2: error: because it uses <filesystem>, we need c++11 or better#error because it uses <filesystem>, we need c++11 or better
When fpl2cc is used outside its own source project, error messages from embedded headers have erroneous and/or misleading paths.
This shows up particularly if you try to compile the generated code using the default clang++ on OSX!
For example:
sunbird:rage chris$ clang++ src/rage.cc -o bin/rageIn file included from src/rage.cc:3:src/util/fs.h:10:2: error: because it uses <filesystem>, we need c++11 or better#error because it uses <filesystem>, we need c++11 or better