[PD-dev] pd-extended installer puts libraries in system32 folder. Is it a bad idea?

Rafael Vega email.rafa at gmail.com
Mon Mar 31 00:41:33 CEST 2014


Hi. First post here :)

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.

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.

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.

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?

My 2 cents.

Thanks!

:)



-- 
Rafael Vega
email.rafa at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20140330/35e04ef2/attachment.htm>


More information about the Pd-dev mailing list