Hey everybody,

Thanks for all of your great work!  I'm new to this project, but very
impressed so far!

My issue is on my Windows 7 box... I downloaded all the git sources over
the weekend and got it building and running just fine on my Ubuntu machine
(12.10) but I'm having issues running my build in Windows. I got everything
to compile (finally) but when it came to run time I realized I did not have
any of the dlls that should live next to the executable, so I tried
grabbing them all from my flightgear 2.8.0.5 binary install.

Of course, it turned out those were all outdated, so I grabbed all new ones
out of the OSG and libsvn projects.  That covered almost all of the dlls in
use, with the exceptions of iconv.dll, gettextlib.dll, gettextsrc.dll, the
msvcr & msvcp dlls, and the PocoFoundation and PocoNet dlls.  (I think
that's all of them anyway.)

The really weird thing is I built it in debug, and when it crashed it was
in msvcr90.dll... I have two versions of msvcr in my game directory
actually, but they are msvcr71 and msvcr100.  I searched around and found
several copies of msvcr90 in my windows system folders, but they seemed to
be mostly in archive folders, while in my system32 and system64 folders I
have only msvcr100 and 110 versions.

Does anyone know why or where windows would be finding msvcr90.dll instead
of the one sitting right next to the program or in the system32 & 64
folders?  Also, would there happen to be any kind of official stockpile of
dlls to grab from when the base project updates one of its dependencies?
Any advice would be much appreciated.

Chris Calef
BrokeAss Games, LLC
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to