Quoting Emil Velikov (2017-10-05 11:26:40) > On 5 October 2017 at 18:12, Dylan Baker <dy...@pnwbakers.com> wrote: > > This has the same problem as the previous commit, generated headers and > > hardcoded paths. > > > Something's strange here. You already have the "generic" > > AM_CPPFLAGS = \ > ... \ > -I$(top_builddir)/src/mapi \ > -I$(top_srcdir)/src/mapi > > ... at the top. Thus you don't need the extra -I directive, nor the > include change. > Where is the file generated with Meson? > > -Emil
<builddir>/src/mapi/glapi/gen Basically because meson generates -I arguments for you it doesn't allow you to specify where generator outputs go, you include the object for the generator in your executable/library sources and it does the rest. There are actually a lot of generators in src/mapi/glapi/gen that I've pulled into odd places in the meson build to work around this design mismatch.
signature.asc
Description: signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
