So I did some investigation on this and I found out the following:<div><br></div><div>user-config.jam looks like:</div><div><br></div><div>using msvc : 7.1 ;</div><div>using stlport : 5.1 : C:/Code/work/rdailey-t510/depot/dev/gfe-dev/server/external/stlport/WINNT5.0_OPT.OBJ/stlport : C:/Code/work/rdailey-t510/depot/dev/gfe-dev/server/external/stlport/WINNT5.0_OPT.OBJ/lib ;</div>
<div><br></div><div>And the command I&#39;m using to build boost is:</div><div><br></div><div>b2 toolset=msvc link=shared threading=multi stdlib=stlport-5.1 --build-type=complete stage</div><div><br></div><div>However during the build process, when the DLL files are being linked, they fail with unresolved externals from STLport. My STLport library is named like so: stlport.5.1.lib</div>
<div><br></div><div>Anyone know why this is failing?<br clear="all"><div><br></div><div>---------</div>Robert Dailey<br>
<br><br><div class="gmail_quote">On Mon, Oct 3, 2011 at 1:45 PM, Robert Dailey <span dir="ltr">&lt;<a href="mailto:rcdailey@gmail.com">rcdailey@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<div><br></div><div>I was searching around Google for this but I wasn&#39;t able to find any documentation. Is there a way to reliably build the latest version of Boost using STLport on Windows instead of letting boost use Microsoft&#39;s STL implementation?</div>

<div><br></div><div>Thanks in advance.<br clear="all"><div><br></div><div>---------</div>Robert Dailey<br>
</div>
</blockquote></div><br></div>