[PATCH modular] Per-component configure options
memsize at videotron.ca
Wed Jan 18 10:16:16 PST 2012
On 12-01-18 11:14 AM, Trevor Woerner wrote:
> I'm surprised nobody seems interested in this patch, I would have
> thought a general mechanism to provide per-component configuration
> options would have been a feature for which people would have been
> waiting; especially the distribution maintainers.
Sorry, I missed this patch. I'll have a look at it.
> I was trying to perform a build from the git repositories on a clean
> installation of a Ubuntu 10.04.3 (LTS) machine and found that I
> couldn't build mesa/mesa successfully without supplying the
> "--enable-nouveau-experimental-api" configuration option when building
I have never been able to build mesa "out-of-the-box". It always needed
some options to not build certain areas.
I noticed from a poster using build.sh that he uses --confflags with all
options. The modules that do not recognise an option simply issues a
warning. This cannot replace the feature you propose but comes in
support of it.
> mesa/drm. On my openSuSE 12.1 machine (which I normally use) the build
> of mesa/mesa gets contaminated by the system headers (which I hadn't
> noticed at the time) which are provided by the libdrm-devel package.
> The Ubuntu 10.04.3 machine doesn't have this header in /usr/include so
> the build fails. In any case a git build shouldn't be contaminated in
> this way.
This same scenario happened to me with the xserver. No -I were provided
for a config test and the system installed headers were used for those
who had the development headers installed. I fixed this.
> Ideally it would be great to perform a sysroot-style build at some
> point to find out what other modules are being contaminated by system
> include files, but that will have to wait until I find the motivation
> and/or time.
Be aware that pkg-config has a default search path that will pick-up .pc
files from the system installed ones. To ensure that you are not
picking-up any headers or libs, export PKG_CONFIG_LIBDIR=/dev/null.
Building from a "server" distro with no X installed is a sure thing.
> xorg-devel at lists.x.org: X.Org development
> Archives: http://lists.x.org/archives/xorg-devel
> Info: http://lists.x.org/mailman/listinfo/xorg-devel
More information about the xorg-devel