[Mesa-dev] last call for autotools

Marek Olšák maraeo at gmail.com
Mon Dec 17 06:08:27 UTC 2018


On Sun, Dec 16, 2018 at 9:19 PM Marek Olšák <maraeo at gmail.com> wrote:

> On Thu, Dec 13, 2018 at 7:48 PM Dylan Baker <dylan at pnwbakers.com> wrote:
>
>> Quoting Marek Olšák (2018-12-13 11:28:10)
>> > Another issue with meson is this:
>> >
>> > I have to set PKG_CONFIG_PATH when I type meson for 32-bit builds. If I
>> do
>> > meson configure --clearcache and then type "ninja", it will
>> reconfigure, but
>> > will use 64-bit libraries instead because PKG_CONFIG_PATH is not set
>> when ninja
>> > is run, which will fail to link.
>> >
>> > Luckily, at least CC="gcc -m32" and CXX="g++ -m32" weren't wiped out by
>> > --clearcache.
>> >
>> > Additionally, it would be nice if the default build type was release
>> instead of
>> > plain.
>> >
>> > Thanks,
>> > Marek
>> >
>> > On Mon, Dec 10, 2018 at 6:11 PM Dylan Baker <dylan at pnwbakers.com>
>> wrote:
>> >
>> >     Meson 0.49.0 has been out for a couple of days now, and I'd like to
>> make
>> >     the
>> >     final call for autotools. My patch is so massive that it's a huge
>> pain to
>> >     send
>> >     to the list, the latest versions is here:
>> >     https://gitlab.freedesktop.org/dbaker/mesa/commits/delete-autotools
>> >
>> >     Dylan
>> >     _______________________________________________
>> >     mesa-dev mailing list
>> >     mesa-dev at lists.freedesktop.org
>> >     https://lists.freedesktop.org/mailman/listinfo/mesa-dev
>> >
>>
>> I've had much better luck using a cross file for doing x86 builds on
>> x86_64, I
>> believe I've posted my cross file before but I can do so again.
>>
>
> Can this possibly be documented in the Mesa docs? The current
> documentation is misleading (LLVM and PKG_CONFIG_PATH sections) and missing
> other information.
>

I think one of the serious usability issues is that environment variables
such as CFLAGS, CXXFLAGS, LDFLAGS, and PKG_CONFIG_PATH are not saved by
meson for future reconfigures. I think meson should ignore the variables
completely, or the Mesa documentation should discourage users from the
setting the variables. The current situation would be acceptable to me if
users were warned that setting environment variables is a trap.

Marek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20181217/6b541ba1/attachment.html>


More information about the mesa-dev mailing list