[Mesa-dev] [PATCH 2/2] configure.ac: drop support for ancient expat versions

Chuck Atkins chuck.atkins at kitware.com
Thu Aug 3 14:29:42 UTC 2017


> So if
> > you did happen to have an older expat version that you manually created a
> > .pc file for, then things should build and work just fine, barring of
> course
> > any expat bugs from untested older versions.  Do I have that right?
> >
> Right - the version and .pc is more of a happy coincidence.
> If one has manually added the file, regardless of the versions things
> should just work.
>

Good.  I figured as much.



> Show does the following sound?
>
> "configure.ac: drop manual detection of expat header/library
>
> Use the .pc file, as provided by version prior 2.1.0 onward and
> dropping the manual header/library check.
> Version 2.1.0 was released back in Mar 2012 and all major distributions
> use it.
>
"
>

That certainly provides more clarity.


Setting the _CFLAGS/_LIBS variables will override the detection...


Great!



> use it wisely ;-)
>

I certainly don't intend to use it but these situations do come come up.
The typical use case is for us is with commercial customers where we're
integrating our stuff into the build of thier product so we in turn need to
sometimes integrate mesa as well.  Hopefully they've propagated the usage
info in the .pc file correctly for the necessary dependencies but if not
(i.e. the "meta" build puts all dependencies into a staging area but does
so by just manually copying libs and headers, so even if it builds a brand
new expat there's no .pc file in the staging area) then it's good to know
how to force it if necessary.

- Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170803/a7d386c2/attachment.html>


More information about the mesa-dev mailing list