Bug 4200 - Modular builds more shared objects than monolithic
Summary: Modular builds more shared objects than monolithic
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Build/Modular (show other bugs)
Version: 7.0.0
Hardware: x86 (IA32) All
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 1690
  Show dependency treegraph
 
Reported: 2005-08-22 18:56 UTC by Nicholas Miell
Modified: 2005-12-19 09:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Nicholas Miell 2005-08-22 18:56:12 UTC
Some libraries are deliberately build static-only in the monolithic tree, while
modular builds shared objects for everything, including what should probably
still be static-only.

This includes (but may not be limited to):

libdmx.so.1.0.0
liboldX.so.6.0.0
libXau.so.6.0.0
libXdmcp.so.6.0.0
Comment 1 Alan Coopersmith 2005-08-24 09:04:51 UTC
libXdmcp & libXau probably should be shared libraries as they are used by a 
number of X servers and display managers.   When the system had a single X 
server and just xdm, making them static made sense, but it doesn't fit as 
well in a world with Xorg, Xnest, Xvfb, Xdmx, Xprint, xdm, gdm, kdm, etc.
Comment 2 Adam Jackson 2005-08-24 12:37:55 UTC
dmx was being left static only because rik and kem weren't finished with the API
yet, but kem says it's ready to be shared now.

taking oldX shared won't hurt, i suppose.
Comment 3 Adam Jackson 2005-08-30 12:44:34 UTC
nonetheless we should build them the same way in the monolith too.
Comment 4 Alan Coopersmith 2005-09-22 16:54:35 UTC
libXau & libXdmcp are now built shared in the monolith as well.
Comment 5 Daniel Stone 2005-12-16 17:31:09 UTC
guess we'll just swallow up the oldX difference?
Comment 6 Adam Jackson 2005-12-20 04:09:03 UTC
yeah, oldX is too small and useless to worry about.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.