Lucas De Marchi

> If you want to #include , then using output: 'mavlink' (the directory) and @OUTDIR@ in the command: should work for you. You can skip the wrapper shell script. This...

It seems the problem is that it's not adding the include from the build directory. I pushed something similar to the suggested changes here: https://github.com/01org/mavlink-router/commits/meson

@nirbheek I saw the patch when you sent and was going to test it now, but it's not there anymore. As far as I remember from the patch, there are...

> We can't revert those changes because they cause build failures for people with newer, stricter compilers and -Werror. Can you try this patch? It's a bit hacky but it...

@dcbaker does that mean it would accept a directory as output? But then what would prevent meson to add e.g. `-Isrc/non-existent-directory` and break the build?

@dcbaker the main problem here is that currently it will add a -I for the source directory and another for the build directory. See https://github.com/mesonbuild/meson/pull/2259#issuecomment-325765576 - we'd need to change...

@dcbaker did you have a chance to try your solution?

@hamishwillee added some suggestions above. Also adding here @jbeyerstedt for feedback since he is cleaning up mavlink-router and improving it a lot lately. My worry is that this has a...

That sounds good. Thanks. Yeah, particularly about the config documentation: we need to move it somewhere. Maybe add a gh-pages and have all the options documented there?

LGTM