On Fri, Mar 29, 2019 at 07:26:10PM +0000, Ken Moffat via blfs-dev wrote:
> On Thu, Mar 28, 2019 at 06:13:01PM -0500, Bruce Dubbs via blfs-dev wrote:
> > In mesa, I did 'mesaon configure' to see the options it understood.
> > What I got was virtually unreadable due to really, really bad formatting
> > for the mesa specific options.
> >
> > Attached is an edited version that is at least a little readable.
> >
> > -- Bruce
>
> > Core properties:
> > Source dir /build/mesa/mesa-19.0.0
> > Build dir /build/mesa/mesa-19.0.0/build
> >
>
> I went to try this, but it does not work until meson has already
> been run!
>
While we are using 0.49.2, the process seems to be (using '..' as
shorthand for "the directory containing meson.build - usually that
is indeed '..' but on at least x265 it differs) :
1. meson ..
2. meson configure | less (tolerable on a wide terminal)
3. meson [ desired options ] --reconfigure ..
And then, having discovered that my previous build had omitted
nouveau, I gave mesa a try using just the 'auto' settings.
The output from meson did not really indicate what it had enabled.
Then I built it - added nouveau drivers, but SMALLER than my
previous build. Rerunning meson configure shows that 'osmesa' was
not enabled. I don't have valgrind installed, that would also be
auto. And gallium-nine is also disabled.
But --sysconfdir seems to be redundant (it should be the default for
/usr, and anyway nothing gets installed in /etc by mesa-19).
So, apart from the possibility of adding -Dbuild-tests=true, for a
full build of all available platforms and drivers, it appears that
there is no need to specify any of -Ddri-drivers=,
-Dgallium-drivers=, -Dplatforms=.
To me, that implies that the options could be reworded. Something
like:
"If you do not specify the drivers and platforms, all available
drivers and platforms **for the X86 architecture** will be
installed. The gallium available drivers ...
... PLATFORMS="x11,wayland,drm"
And add the following to the meson command below:
-Ddri-drivers=$DRI_DRIVERS \
-Dgallium-drivers=$GALLIUM_DRV \
-Dplatforms=$PLATFORMS \
and unset those variables afterwards."
That looks horribly messy, but ensures that by default all available
drivers and platforms will be automatically selected.
ĸen
--
It is said that there are two great unsolved problems in computer
science: naming, cache invalidation, and off-by-one errors.
-- Ben Bullock
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
