Bug 447 - RFE: Build a static version of the STSF/Xft bridge additionally to the shared library version
Summary: RFE: Build a static version of the STSF/Xft bridge additionally to the shared...
Status: RESOLVED WONTFIX
Alias: None
Product: STSF
Classification: Unclassified
Component: XST: Xft bridge (show other bugs)
Version: unspecified
Hardware: All All
: high enhancement
Assignee: STSF mailinglist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-10 02:05 UTC by Roland Mainz
Modified: 2004-04-12 19:42 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Roland Mainz 2004-04-10 02:05:59 UTC 
RFE: Build a static version of the STSF/Xft bridge additionally to the shared
library version. That will get rid of at least one shared library dependicy and
the applications do not need a libXft.so anymore lying around.
Comment 1 Alexander Gelfenbain 2004-04-12 19:52:48 UTC 
Alan, do we want to do it?
Comment 2 Alan Coopersmith 2004-04-12 20:27:16 UTC 
I believe the official Sun position is that static libraries and static linking
is akin to evil incarnate.

We definitely won't be shipping a static version in Solaris, but if someone
using the source release wanted to build a static version, it should be as
simple as adding '#define NormalLibXft YES' to xc/config/cf/host.def (assuming
building in the X tree, as we do for the Solaris version - for the standalone
version you probably need to add it to localdefines in the xftbridge directory,
but since I've never built it, I don't know how it's expected to be built).
Comment 3 Roland Mainz 2004-04-13 10:33:34 UTC 
Alexander:
Why the WONTFIX ?
Comment 4 Alexander Gelfenbain 2004-04-13 12:42:45 UTC 
Alan's comment provides sufficient information about how to build STSF static
libraries, so I will include it into INSTALL.TXT file. I don't feel there is
anything else that needs to be done.

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.