From: Aleksey Gurtovoy (alexy_at_[hidden])
Date: 2004-10-11 12:16:22
Given the current definitions of BOOST_VERSION in "Jamrules":
BOOST_VERSION ?= 1.32.0 ;
and BOOST_LIB_VERSION in "boost/version.hpp":
#define BOOST_LIB_VERSION "1_32"
I don't see how the current code in "common-variant-tag" rule
local version-tag = ;
if ! $(gUNVERSIONED_VARIANT_TAG)
{
local version-number = [ get-values <version> : $(properties) ] ;
version-number ?= $(BOOST_VERSION) ;
version-tag = [ MATCH "^([^-]+)[.]([^-]+)" : $(version-number[1]) ] ;
version-tag = $(version-tag:J="_") ;
}
can produce names matching the ones requested in "boost/config/auto_link.hpp".
The difference in the versions' format is bound to cause the former
to return something like "whatever-toolsettag-mt-1.32_0" and "auto_link.hpp"
to request "whatever-toolsettag-mt-1_32".
Am I missing something?
-- Aleksey Gurtovoy MetaCommunications Engineering