[Mesa-dev] [PATCH] RFC: meson: Add a new build-dev-tools option

[Eric Engestrom]

On Saturday, 2017-11-11 14:39:20 -0800, Jason Ekstrand wrote:
> On Sat, Nov 11, 2017 at 10:30 AM, Rob Clark <robdclark at gmail.com> wrote:
> 
> > On Sat, Nov 11, 2017 at 12:42 PM, Jason Ekstrand <jason at jlekstrand.net>
> > wrote:
> > > A variety of the different drivers in mesa have some sort of developer
> > > tools to go along with them.  Normal users don't want these but devs do.
> > > This commit adds a new build-dev-tools option which causes these tools
> > > to be built and installed.
> >
> > fwiw, nouveau and etnaviv also have standalone compilers
> >
> > And I kinda think mesa already has too many build config options
> > already,
> 
> 
> Yeah...  that may be. I've stopped noticing as I just have a build script
> that does it all for me (and, incidentally works with both autotools and
> meson).
> 
> 
> > so maybe tying these to debug build would be a reasonable way
> > to avoid adding another.. I don't insist on it if someone else has a
> > reason to build their driver's "dev tools" outside of a debug build,
> > but I really only have use for ir3compiler in the context of a debug
> > build.
> >
> 
> Maybe...  However, the aubinator tools that we have are something you may
> want to at least use with a release build.  Whether or not there's any
> point in building them in release mode, I don't know.  Sometimes it is
> useful to use the aubinator out of the same branc as you're hacking on.

This only affects whether it's built by default, you can always run
`ninja src/intel/tools/aubinator` manually on your release build :)

I agree with tying this to whether it's a release build or not, although
I would also exclude 'plain' used in packages, which really just leaves
debug builds:

	build_dev_tools = get_option('buildtype').startswith('debug')