[osg-users] broken osgconv.exe
helsing72 at gmail.com
Thu Nov 26 13:00:41 PST 2009
Hi Ted, J-S, all,
First - all creds and kudos for the vc90 binary win32 2.8.2 packages
to Sukender, not me.
Second - did you (Ted) sort this out? Can we drop it or do you still
On Wed, Nov 25, 2009 at 1:03 PM, Mattias Helsing <helsing72 at gmail.com> wrote:
> Hi again Ted,
> I can't find any dll that depends on msvc*80 runtime dll but may have
> some clues to a solution.
> On Tue, Nov 24, 2009 at 9:03 PM, ted morris <ted.morris at gmail.com> wrote:
>> Yes, I think I resolved finding the 3rdparty dependencies. But for some
>> reason, the osgdb_xxx pluggins listed in the last e-mail:
> These all depend on zlib1.dll, which on my system depend correctly on
> msvcp90.dll. I'm guessing that somehow your system picks up some other
> zlib1. The zlib module is very common so there is a good chance you
> already got it embedded with other software. Try setting the PATH
> explicitly like:
> set PATH=<vc90_dependencis>\bin;<vc90_osg>\bin
> before running dependency walker or osgviewer
>> dependencywalker shows that these pluggin dlls are still looking for
>> MSVCR80.DLL *and* MSVCR90.DLL
> No, osgdb_tiff, _curl and the other plugin in your list depends on
> msvcr90.dll. However they also depend on many other modules that may,
> in turn, depend on whatever runtime they were compiled against.
> Hitting f9 in dependency walker will show you the full path to all
> listed dlls
>> And the other pluggins can't find MSVCR90.DLL.
> I think this is a flaw in dependency walker. I don't have your system,
> but my system reports this too where top dependency msvcp90 depends on
> msvcr90. If this is the case also for you then just ignore.
> I'm dropping this for now since I can't find anything wrong with the
> binaries on the website. Drop me screenshots, text logs or whatever
> and I'll investigate further.
>> Well, I tried dependencywalker.com and opened up the pluggins.
>> On Mon, Nov 23, 2009 at 7:24 PM, Mourad Boufarguine
>> <mourad.boufarguine at gmail.com> wrote:
>>> Hi Ted,
>>> You can use the Dependency Walker (http://www.dependencywalker.com/) to
>>> check the version number of the runtime, the dependencies were compiled
>>> I just tried it with the zlib and png dlls contained in "VisualStudio 9
>>> (2008) SP1" prebuild dependencies
>>> and I found that the release versions were compiled with the 9.0.30729
>>> runtime, which is actually "2008 SP1". The debug version, though, was
>>> compiled with the 9.0.21022 runtime , which is the "2008" runtime. The zlib
>>> is used in both ive and gz plugins. I don't see how you get the message
>>> about the 2005 runtime dependency. Double check in the "output" window of VS
>>> that the zlib and png dlls that are actually loaded are the good ones.
>>> On Tue, Nov 24, 2009 at 1:21 AM, ted morris <ted.morris at gmail.com> wrote:
>>>> credist_x86 VisualStudio 2005 (v8) runtimes
>>> osg-users mailing list
>>> osg-users at lists.openscenegraph.org
>> osg-users mailing list
>> osg-users at lists.openscenegraph.org
More information about the osg-users