<div dir="ltr"><div><div>Hi. First post here :)<br></div><br>I just spent a couple of hours figuring out why a c++ program I compiled on windows (not my main OS) would not run. I am linking my program with libstdc++ and compiling with the MinGW toolset.<br>
</div><div><br>Now, I have pd-extended installed on the same machine and when it installed, it put it's own copy of libstdc++ in c:\WINDOWS\system32. The way Windows loads libraries is: first looks on the directory where the exe is, then it looks on the system folder and then it looks on the PATH.<br>
<br></div><div>The problem with my program was, then, that the MinGW linker did not like the version of libstdc++ put in the system folder by pd-extended installer. Uninstalling pd-extended "fixed" the issue.<br>
<br></div><div>So, I just want to throw this out there: Should the pd-extended installers avoid putting libraries on the system folder to avoid this kind of confusion?<br></div><div><br>My 2 cents.<br></div><div><br>Thanks! <br>
<br>:)<br></div><div><div><br><br clear="all"><div><br>-- <br><div dir="ltr"><div>Rafael Vega<br></div><a href="mailto:email.rafa@gmail.com" target="_blank">email.rafa@gmail.com</a></div>
</div></div></div></div>