[PATCH libX11] config: Add an option to initialize threads by default.

Alan Coopersmith alan.coopersmith at oracle.com
Mon Jan 31 11:11:22 PST 2011

On 01/31/11 02:46 AM, Rami Ylimäki wrote:
> It's sometimes impossible to know in advance whether an X client is
> using Xlib from multiple threads or not. For example, there could be
> some generic X client that acts as a plugin container. Plugins could
> be loaded to the container at runtime, but the container doesn't know
> whether the plugins are using Xlib from a separate thread or not.

I don't know if it's a better answer, but an alternate solution we've
been carrying around in Solaris libX11 since long before I got here is
to allow XInitThreads() to be called by other plugins/libraries even after
the X connection is up and running.    I've not checked how well it works
in the current world where half of XlibInt.c was ripped out and replaced
by xcb calls, but the code is available if someone wants to look at it.

Original version:

Current version:

	-Alan Coopersmith-        alan.coopersmith at oracle.com
	 Oracle Solaris Platform Engineering: X Window System

More information about the xorg-devel mailing list