[Boost-build] [bbv2] Problems using msvc-config.jam

From: Foster Brereton (fosterb.boost_at_[hidden])
Date: 2006-01-30 20:27:11

We are using BBv2 to build a suite of libraries and applications using
both MSVC 7.1 and MSVC 8. We're trying to set up a resource compiler
flag to give RC a hint as to what version it should be compiling for,
in order that we can get a manifest file issue resolved. The patch is
as follows:

diff -ruN boost_1_33_1/tools/build/v2/tools/msvc.jam
boost/tools/build/v2/tools/msvc.jam
--- boost_1_33_1/tools/build/v2/tools/msvc.jam	2005-07-15
06:35:58.000000000 -0700
+++ boost/tools/build/v2/tools/msvc.jam	2006-01-05 16:10:50.000000000 -0800
@@ -164,7 +164,25 @@
     {
         flags msvc.compile CFLAGS $(condition)/<optimization>speed :
/Ogity /O2 /Gs ;
         flags msvc.compile CFLAGS $(condition)/<optimization>space :
/Ogisy /O1 /Gs ;
-    }
+    }
+
+	#
+	# ADOBE	:	This change allows for a version to be set inside the RC
+	#			compiler so we can include version-dependent manifest files
+	#
+
+	if ! [ MATCH ^([67].*) : $(version) ]
+	{
+		flags msvc.compile.rc DEFINES : "ADOBE_VER=8 " ;
+	}
+	else
+	{
+		flags msvc.compile.rc DEFINES : "ADOBE_VER=7 " ;
+	}
+
+	#
+	# ADOBE	:	End changes
+	#
 }

 rule default-paths ( version ? )

Or problem is this: irrespective of the compiler for which we are
targeting, the resource compiler gets both "-DADOBE_VER=7" *and*
"-DADOBE_VER=8". Are there any insights into this issue of which we
are not aware?

Blessings,
Foster

--
Foster T. Brereton - Computer Scientist
Software Technology Lab, Adobe Systems Incorporated
fbrereto_at_[hidden]   --   http://opensource.adobe.com