+Daniel (14 October 2005)
+- Reverted the LIBCURL_VERSION_NUM change from October 6. As Dave Dribin
+ reported, the define is used by the configure script and is assumed to use
+ the 0xYYXXZZ format. This made "curl-config --vernum" fail in the 7.15.0
+ release version.
+
Version 7.15.0 (13 October 2005)
Daniel (12 October 2005)
This release includes the following bugfixes:
- o
+ o curl-config --vernum fixed
Other curl-related news since the previous public release:
This release would not have looked like this without help, code, reports and
advice from friends like these:
- o
+ Dave Dribin
Thanks! (and sorry if I forgot to mention someone)
and it is always a greater number in a more recent release. It makes
comparisons with greater than and less than work.
*/
-#define LIBCURL_VERSION_NUM ((LIBCURL_VERSION_MAJOR << 16) | \
- (LIBCURL_VERSION_MINOR << 8) | \
- LIBCURL_VERSION_PATCH)
+#define LIBCURL_VERSION_NUM 0x070f01
#endif /* __CURL_CURLVER_H */
# Replace version number in header file:
sed -e 's/^#define LIBCURL_VERSION .*/#define LIBCURL_VERSION "'$libversion'"/g' \
+ -e 's/^#define LIBCURL_VERSION_NUM .*/#define LIBCURL_VERSION_NUM 0x'$numeric'/g' \
-e 's/^#define LIBCURL_VERSION_MAJOR .*/#define LIBCURL_VERSION_MAJOR '$major'/g' \
-e 's/^#define LIBCURL_VERSION_MINOR .*/#define LIBCURL_VERSION_MINOR '$minor'/g' \
-e 's/^#define LIBCURL_VERSION_PATCH .*/#define LIBCURL_VERSION_PATCH '$patch'/g' \