Quoting Emil Velikov (2017-10-13 13:20:37)
> On 13 October 2017 at 19:13, Dylan Baker wrote:
> > Quoting Emil Velikov (2017-10-13 08:35:47)
> >> From: Emil Velikov
> >>
> >> Currently all the build systems but Meson generate the header in
> >> src/mapi/glapi. Meson cannot do that since:
> >> - i
On 13 October 2017 at 19:13, Dylan Baker wrote:
> Quoting Emil Velikov (2017-10-13 08:35:47)
>> From: Emil Velikov
>>
>> Currently all the build systems but Meson generate the header in
>> src/mapi/glapi. Meson cannot do that since:
>> - it does not allow user control over the location of output
Quoting Emil Velikov (2017-10-13 08:35:47)
> From: Emil Velikov
>
> Currently all the build systems but Meson generate the header in
> src/mapi/glapi. Meson cannot do that since:
> - it does not allow user control over the location of output files
> - moving the generation rule(s) causes explos
For list posterity:
Reviewed-by: Dylan Baker
Quoting Emil Velikov (2017-10-13 08:35:47)
> From: Emil Velikov
>
> Currently all the build systems but Meson generate the header in
> src/mapi/glapi. Meson cannot do that since:
> - it does not allow user control over the location of output files
>
Tested-by: Mark Janes
Emil Velikov writes:
> From: Emil Velikov
>
> Currently all the build systems but Meson generate the header in
> src/mapi/glapi. Meson cannot do that since:
> - it does not allow user control over the location of output files
> - moving the generation rule(s) causes exp
From: Emil Velikov
Currently all the build systems but Meson generate the header in
src/mapi/glapi. Meson cannot do that since:
- it does not allow user control over the location of output files
- moving the generation rule(s) causes explosion due to the unusual
structure of glapi and friends