Re: [Intel-gfx] [PATCH i-g-t 2/3] meson: gtkdoc support

2018-03-06 Thread Daniel Vetter
On Thu, Feb 22, 2018 at 03:54:09PM -0800, Eric Anholt wrote: > Daniel Vetter writes: > > > Bunch of neat improvements: > > > > - xml generates correctly depend upon the test binaries > > - no need to re-run autogen.sh when new chapters/functions get added, > > all

Re: [Intel-gfx] [PATCH i-g-t 2/3] meson: gtkdoc support

2018-02-22 Thread Eric Anholt
Daniel Vetter writes: > Bunch of neat improvements: > > - xml generates correctly depend upon the test binaries > - no need to re-run autogen.sh when new chapters/functions get added, > all handed by meson I just rebased on top of this commit, and now my cross build

[Intel-gfx] [PATCH i-g-t 2/3] meson: gtkdoc support

2017-12-05 Thread Daniel Vetter
Bunch of neat improvements: - xml generates correctly depend upon the test binaries - no need to re-run autogen.sh when new chapters/functions get added, all handed by meson Still one issue: - the gtkdoc target doesn't depend upon the custom_target yet, hacked around using build_by_default:

Re: [Intel-gfx] [PATCH i-g-t 2/3] meson: gtkdoc support

2017-12-05 Thread Petri Latvala
On Mon, Dec 04, 2017 at 09:48:36PM +0100, Daniel Vetter wrote: > Bunch of neat improvements: > > - xml generates correctly depend upon the test binaries > - no need to re-run autogen.sh when new chapters/functions get added, > all handed by meson > > Still one issue: > > - the gtkdoc target

[Intel-gfx] [PATCH i-g-t 2/3] meson: gtkdoc support

2017-12-04 Thread Daniel Vetter
Bunch of neat improvements: - xml generates correctly depend upon the test binaries - no need to re-run autogen.sh when new chapters/functions get added, all handed by meson Still one issue: - the gtkdoc target doesn't depend upon the custom_target yet, hacked around using build_by_default: