Summary: | 1.0 release should use libxcb.so.1 | ||
---|---|---|---|
Product: | XCB | Reporter: | Jamey Sharp <jamey> |
Component: | Library | Assignee: | Josh Triplett <josh> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | highest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 6797 |
Description
Jamey Sharp
2006-02-21 16:16:14 UTC
You can add version stuff of libtool in src/Makefile.am. Either : libXCB_la_LDFLAGS = -release 0.9.0 or maybe better: libXCB_la_LDFLAGS = -release $(PACKAGE_VERSION).0 to use the usual major.minor.micro version of autoconf. Or libXCB_la_LDFLAGS = -version-info 1:0:0 to use the current.revision.age version of libtool. There's something strange with the last one : When I do : libXCB_la_LDFLAGS = -version-info 0:9:0 I get libXCB.0.0.9. I don't understand why. See the comment in xcb/src/Makefile.am for an explanation of the libtool -version-info flag. We released XCB 0.9 as libXCB.so.0.0.0; this will change to libXCB.so.1 with the 1.0 release when we drop all deprecated functions at that point. It should then hopefully never change, with any deprecated functions remaining indefinitely. We have now released libxcb 1.0RC1 (which used libxcb.so.0) and 1.0RC2 (which used libxcb.so.1). Barring some horrible bug which requires an ABI bump to fix (highly unlikely) we will release 1.0 with the same soname as 1.0RC2, libxcb.so.1, and close this bug at that time. retitled bug We've released XCB 1.0, and it uses libxcb.so.1. Marking this as fixed. |
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.