title: Poco as static library with dynamic runtime requires import library of DLL?
body: <p>I'm trying to use Poco as a static library with dynamic runtime inside my project. I've downloaded the complete sources of Poco 1.7.3 and used the <code>buildwin.bat</code> script to compile the libraries using my self-compiled OpenSSL 1.0.2h shared library (i.e. adjusted the path in <code>buildwin.bat</code>).</p>
  
  <p>Producing <code>PocoXYZmd.lib</code> via <code>buildwin.bat 140 build static_md debug Win32 nosamples notests msbuild</code> works fine.</p>
  
  <p>However, when I try to link against <code>PocoXYZmd.lib</code> inside my own project, the linker searches for <code>PocoXYZ.lib</code>, the import library for <code>PocoXYZ.dll</code>.</p>
  
  <p>Building Poco with <code>shared</code> and providing the <code>PocoXYZ.lib</code> import libraries within the linker search path, I'm getting errors on Poco symbols being already defined (obviously).</p>
  
  <p>Am I missing something crucial or is it a bug in Poco's build script?</p>
  
  <hr>
  
  <p>I've configured Poco to ONLY build the following components: Foundation, XML, JSON, Util, Net, Crypto, NetSSL_OpenSSL.</p>
  
  <p>In addition, I had to adjust the v140 <code>vcxproj</code>-files of Crypto and NetSSL_OpenSSL to link to <code>libeay32.lib</code> and <code>ssleay32.lib</code> (the import libraries for the OpenSSL DLLs) instead of <code>libeay32md.lib</code> and <code>ssleay32md.lib</code> (no idea where these could come from based on the OpenSSL 1.0.2h build scripts).</p>
  
  <p>I'm using Visual Studio 2015 Update 2 on Windows 7, doing everything within the 32bit Visual Studio Developer Prompt.</p>