<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi everyone,</div>
<div> </div>
<div>I am a novice in gstreamer and I am evaluating the toolchain how to integrate it int our Windows delevopment environment,</div>
<div>so sorry in advance for an ignorance related to gstreamer.</div>
<div> </div>
<div>The default gstreamer SDK binaries are linked against MSVCRT.DLL</div>
<div>I think also because the dependencies of gstreamer are also linked against this DLL, e.g. glib-2.0.</div>
<div> </div>
<div>When I would like to write now a plugin with VS 2013 Compiler in C++ (also using C++ std libraries) and only declaring</div>
<div>the gstreamer plugin interface as C, I will get my application linked against MSVCRT120.DLL.</div>
<div> </div>
<div>MyPlugin.DLL => MSVCRT120.DLL</div>
<div>gstreamer => MSVCRT.DLL</div>
<div> </div>
<div>The problem is now, that this will result into linking multiple different runtime libraries, which is evil: http://siomsystems.com/mixing-visual-studio-versions/</div>
<div> </div>
<div>My question is now:</div>
<div>1)</div>
<div>Is it okay to still do this, when I carfully develop my plugin? Or will it definitely result in some problems because of some interfaces of gstreamer where data is given across DLL boundaries?</div>
<div>Does anybody have experience with this kind of tool chain?</div>
<div>
<div>Regards,</div>
<div>Zack</div>
</div></div></body></html>