[Mesa-dev] [PATCH 9/9] meson: build gallium based osmesa
dylan at pnwbakers.com
Fri Oct 27 17:59:52 UTC 2017
Quoting Eric Engestrom (2017-10-27 02:28:05)
> On Thursday, 2017-10-26 13:55:35 -0700, Dylan Baker wrote:
> > Quoting Eric Engestrom (2017-10-26 02:40:20)
> > > On Wednesday, 2017-10-25 15:58:23 -0700, Dylan Baker wrote:
> > > > +if with_shared_glapi
> > > > + osmesa_link_with += libglapi
> > > > +endif
> > > > +if with_ld_version_script
> > > > + osmesa_link_args += [
> > > > + '-Wl,--version-script', join_paths(meson.current_source_dir(), 'osmesa.sym')
> > >
> > > files('osmesa.sym') ?
> > > I'm not sure if it would work here though, since it expects a string.
> > > /me hopes meson converts the file_array to a list of its filenames
> > >
> > files() doesn't work here. Maybe it makes sense to extend meson to support that?
> We're not the first ones to think about this :)
> There's already an issue open for this exact case , which doesn't really
> have a conclusion. Might be worth chiming in, if only to ping them?
>  https://github.com/mesonbuild/meson/issues/1592
I kinda hacked something up real quick. I don't think it would be hard to
implement, although I started wondering about it. Part of what makes File so
special is that it always works no matter what directory you're in. I don't
think that th right thing is to be able to us them in string.format, but to be
able to pass them as a linker or compiler argument, and have that do the right
thing with them. I'll look into that more.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
More information about the mesa-dev