id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
4349	Autolinking against debug STLport	eckhardt@…	Dave Abrahams	"I can't use autolinking with the following setup:
 * using a debug build
 * using STLport
 * not using additional checks and diagnostics (_STLP_DEBUG)

The autolinking code should simply look for the ""dp"" variant of the Boost libraries. What I get is a warning that these libs are not built by default. Even worse, I get an error downright refusing to link with that version, even though I did compile them. However, that error is still better than nothing, because the macros defining the version are then set to ""gdp"" which is simply incompatible with my settings.

Things to fix:
 * Fix the generated tags, i.e. replace ""gdp"" with ""dp"" for above example.
 * Don't generate an error when using STLport with debug symbols but without additional diagnostic.

Further things that could be fixed, too:
 * Don't output a warning unless lib diagnostics (BOOST_LIB_DIAGNOSTIC) are actually requested.
 * Document the meaning of an 'n' in the generated tag.
 * Remove redundant comment documenting the 'p' in the generated tag.
 * Fix spelling of STLport here, without a capital P.
 * Fix warnings, those claim that you should use ""/D_STLP_DEBUG=1"", but a simple ""/D_STLP_DEBUG"" is sufficient. A short grep shows that several other parts of Boost also have this, maybe creating separate ticket and patch would be a better choice for this.
 * Fix indention of preprocessor commands, large parts use 3 spaces, some parts use 4.

Concerning the version, this bug is present in today's trunk, 1.43 and 1.33.1, which are also all versions I checked. Concerning 1.33.1, we are using a local version where this discrepancy is fixed and have not found any problems with it.
"	Bugs	new	To Be Determined	Getting Started Guide	Boost Development Trunk	Problem			doomster@…