RE: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Frank: Part of the problem seems to be in the debug version of GEOS. I don't know exactly where at this point. When I use the geos_c.dll you posted ogrinfo works ok. If I make a release version of GEOS then it works but if I make a debug version I get the error message. I don't need the debug version of GEOS at this point so I will continue with the release version. That takes care of the C++ issues but the C# programs don't work on the 64 bit Vista system. Everything works fine on our older systems running XP Thanks for your help Bruce -Original Message- From: Frank Warmerdam [mailto:warmer...@pobox.com] Sent: Tuesday, December 16, 2008 4:41 PM To: Clay, Bruce Cc: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista? Clay, Bruce wrote: > Frank: > I am trying to run ogrinfo from the GDAL build app directory. I did > not have a problem with this until my computer died and I had to get a > new one with you guessed it Vista. It is a 64 bit system running 64 bit > Vista so that may be part of the problem. > > Did you build with the manifest as part of the build process or just add > it to the runtime directory? Bruce, The Microsoft.VC90.CRS.manifest is part of the runtime, and I copy it from the runtime directory (as well as the runtime DLLs). The GDAL16.DLL and executables also all have manifests generated automatically by VC, and the makefiles have an explicit step to embed the manifests into the DLL and executables using the "mt" command. eg. ogrinfo.exe:ogrinfo.cpp $(GDALLIB) $(XTRAOBJ) $(CC) $(CFLAGS) $(XTRAFLAGS) ogrinfo.cpp $(XTRAOBJ) $(LIBS) \ /link $(LINKER_FLAGS) if exist $...@.manifest mt -manifest $...@.manifest -outputresource:$@;1 > Did you build the whole package with VS 2008 nor just the GEOS portion? Only GEOS was built with VS2008. The rest was built with VS2003. > I have run into other problems on this computer mainly with drivers. My > Microsoft finger print reader is not supported on 64 bit. It makes me > wonder just what MS is thing some times, actually most of the time. > They keep changing things that don't help at all. I am sure they have good reasons for the things they do, but MS improvements often just feel like churn to me. All this manifest stuff has certainly been a big hassle, breaking a reasonably understandable model of how DLLs work. Best regards, -- ---+ -- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended recipient, you may not use, copy, disclose, or distribute this message or its contents or enclosures to any other person and any such actions may be unlawful. Ball reserves the right to monitor and review all messages and enclosures sent to or from this email address. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Clay, Bruce wrote: Frank: I am trying to run ogrinfo from the GDAL build app directory. I did not have a problem with this until my computer died and I had to get a new one with you guessed it Vista. It is a 64 bit system running 64 bit Vista so that may be part of the problem. Did you build with the manifest as part of the build process or just add it to the runtime directory? Bruce, The Microsoft.VC90.CRS.manifest is part of the runtime, and I copy it from the runtime directory (as well as the runtime DLLs). The GDAL16.DLL and executables also all have manifests generated automatically by VC, and the makefiles have an explicit step to embed the manifests into the DLL and executables using the "mt" command. eg. ogrinfo.exe:ogrinfo.cpp $(GDALLIB) $(XTRAOBJ) $(CC) $(CFLAGS) $(XTRAFLAGS) ogrinfo.cpp $(XTRAOBJ) $(LIBS) \ /link $(LINKER_FLAGS) if exist $...@.manifest mt -manifest $...@.manifest -outputresource:$@;1 Did you build the whole package with VS 2008 nor just the GEOS portion? Only GEOS was built with VS2008. The rest was built with VS2003. I have run into other problems on this computer mainly with drivers. My Microsoft finger print reader is not supported on 64 bit. It makes me wonder just what MS is thing some times, actually most of the time. They keep changing things that don't help at all. I am sure they have good reasons for the things they do, but MS improvements often just feel like churn to me. All this manifest stuff has certainly been a big hassle, breaking a reasonably understandable model of how DLLs work. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
RE: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Frank:
I am trying to run ogrinfo from the GDAL build app directory. I did
not have a problem with this until my computer died and I had to get a
new one with you guessed it Vista. It is a 64 bit system running 64 bit
Vista so that may be part of the problem.
Did you build with the manifest as part of the build process or just add
it to the runtime directory?
Did you build the whole package with VS 2008 nor just the GEOS portion?
I have run into other problems on this computer mainly with drivers. My
Microsoft finger print reader is not supported on 64 bit. It makes me
wonder just what MS is thing some times, actually most of the time.
They keep changing things that don't help at all.
-Original Message-
From: Frank Warmerdam [mailto:warmer...@pobox.com]
Sent: Tuesday, December 16, 2008 3:13 PM
To: Clay, Bruce
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Clay, Bruce wrote:
> Frank:
> What is the secret to getting GDAL to build this way? I have Visual
> Studio 2005 and have not been able to get it to run. The zip file you
> posted works fine on my system (Vista 64 Bit) but it does not include
> the csharp files so I have to build.
>
> I have tried building with the makefile.vc file and with the solution
> file.
> In both cases it compiles fine but won't run. I get an error popup
when
> I try to run ogrinfo that says
>
> "An application has made an attempt to load the C runtime library
> without using a manifest. This is an unsupported way to load Visual
> Studio C++ libraries" etc.
Bruce,
I'm not sure what issue(s) you are running into exactly. Is this just
running something like gdalinfo that you build against the GDAL16.DLL
that you built?
The only "special" thing I do for the GEOS part of the build which I
build with visual studio 9 (aka 2008 express I think) was to ensure
I distributed the msvcp90.dll and msvcr90.dll along with the
corresponding
Microsoft.VC90.CRS.manifest.
I think that Visual Studio 2005 is VC8, so there should be a
corresponding
msvc{r,p}80.dll you would need with it, and perhaps a corresponding
manifest. I haven't been using VS2005 much though so I'm not so sure.
These issues (needing a manifest) don't exist with older visual studio
versions.
Best regards,
--
---+
--
I set the clouds in motion - turn up | Frank Warmerdam,
warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| Geospatial Programmer for Rent
This message and any enclosures are intended only for the addressee. Please
notify the sender by email if you are not the intended recipient. If you are
not the intended recipient, you may not use, copy, disclose, or distribute this
message or its contents or enclosures to any other person and any such actions
may be unlawful. Ball reserves the right to monitor and review all messages
and enclosures sent to or from this email address.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Clay, Bruce wrote:
Frank:
What is the secret to getting GDAL to build this way? I have Visual
Studio 2005 and have not been able to get it to run. The zip file you
posted works fine on my system (Vista 64 Bit) but it does not include
the csharp files so I have to build.
I have tried building with the makefile.vc file and with the solution
file.
In both cases it compiles fine but won't run. I get an error popup when
I try to run ogrinfo that says
"An application has made an attempt to load the C runtime library
without using a manifest. This is an unsupported way to load Visual
Studio C++ libraries" etc.
Bruce,
I'm not sure what issue(s) you are running into exactly. Is this just
running something like gdalinfo that you build against the GDAL16.DLL
that you built?
The only "special" thing I do for the GEOS part of the build which I
build with visual studio 9 (aka 2008 express I think) was to ensure
I distributed the msvcp90.dll and msvcr90.dll along with the corresponding
Microsoft.VC90.CRS.manifest.
I think that Visual Studio 2005 is VC8, so there should be a corresponding
msvc{r,p}80.dll you would need with it, and perhaps a corresponding
manifest. I haven't been using VS2005 much though so I'm not so sure.
These issues (needing a manifest) don't exist with older visual studio
versions.
Best regards,
--
---+--
I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| Geospatial Programmer for Rent
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
RE: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Frank: What is the secret to getting GDAL to build this way? I have Visual Studio 2005 and have not been able to get it to run. The zip file you posted works fine on my system (Vista 64 Bit) but it does not include the csharp files so I have to build. I have tried building with the makefile.vc file and with the solution file. In both cases it compiles fine but won't run. I get an error popup when I try to run ogrinfo that says "An application has made an attempt to load the C runtime library without using a manifest. This is an unsupported way to load Visual Studio C++ libraries" etc. Bruce -Original Message- From: gdal-dev-boun...@lists.osgeo.org [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Frank Warmerdam Sent: Monday, December 15, 2008 7:42 PM To: Jason Roberts Cc: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista? Jason Roberts wrote: > Phil, > > Thanks for the suggestion. I suspect it will work. My XP SP3 machine has > VC90 entries in C:\Windows\WinSxS, while my Vista SP1 machine does not. > > But if GDAL requires the user to install the VC++ redistributable first, why > is GDAL redisting the DLLs (e.g. msvcr90.dll) in the GDAL\bin directory? I > suspect the intent was to override sxs in the build process, or specify a > publisher policy, or something, so that the user does not have to install > the redistributable themselves. The idea being that GDAL would work like > old-school, pre-sxs applications, where you just have to have the right DLL > versions in the same directory as your .exe. > > Was that not the intent? Are users indeed expected to install that > redistributable first? Jason, My fault. The package includes the required VC9 DLLs, but I neglected to include the manifest for them (Microsoft.VC90.CRT.manifest). I have repackaged the kit with that manifest, and I'd appreciate your testing it. http://download.osgeo.org/gdal/win32/1.6/gdalwin32exe160.zip Best regards, -- ---+ -- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended recipient, you may not use, copy, disclose, or distribute this message or its contents or enclosures to any other person and any such actions may be unlawful. Ball reserves the right to monitor and review all messages and enclosures sent to or from this email address. ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
RE: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
No worries. The ZIP you provided appears to work fine. I uninstalled the VC redistributable and verified that the old package failed again, and then tried the new one, which worked. I'll let you know if I notice anything else. Thanks for the quick action, guys! Jason -Original Message- From: Frank Warmerdam [mailto:warmer...@pobox.com] Sent: Monday, December 15, 2008 7:42 PM To: Jason Roberts Cc: 'Philippe Vachon'; gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista? Jason Roberts wrote: > Phil, > > Thanks for the suggestion. I suspect it will work. My XP SP3 machine has > VC90 entries in C:\Windows\WinSxS, while my Vista SP1 machine does not. > > But if GDAL requires the user to install the VC++ redistributable first, why > is GDAL redisting the DLLs (e.g. msvcr90.dll) in the GDAL\bin directory? I > suspect the intent was to override sxs in the build process, or specify a > publisher policy, or something, so that the user does not have to install > the redistributable themselves. The idea being that GDAL would work like > old-school, pre-sxs applications, where you just have to have the right DLL > versions in the same directory as your .exe. > > Was that not the intent? Are users indeed expected to install that > redistributable first? Jason, My fault. The package includes the required VC9 DLLs, but I neglected to include the manifest for them (Microsoft.VC90.CRT.manifest). I have repackaged the kit with that manifest, and I'd appreciate your testing it. http://download.osgeo.org/gdal/win32/1.6/gdalwin32exe160.zip Best regards, -- ---+ -- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Jason Roberts wrote: Phil, Thanks for the suggestion. I suspect it will work. My XP SP3 machine has VC90 entries in C:\Windows\WinSxS, while my Vista SP1 machine does not. But if GDAL requires the user to install the VC++ redistributable first, why is GDAL redisting the DLLs (e.g. msvcr90.dll) in the GDAL\bin directory? I suspect the intent was to override sxs in the build process, or specify a publisher policy, or something, so that the user does not have to install the redistributable themselves. The idea being that GDAL would work like old-school, pre-sxs applications, where you just have to have the right DLL versions in the same directory as your .exe. Was that not the intent? Are users indeed expected to install that redistributable first? Jason, My fault. The package includes the required VC9 DLLs, but I neglected to include the manifest for them (Microsoft.VC90.CRT.manifest). I have repackaged the kit with that manifest, and I'd appreciate your testing it. http://download.osgeo.org/gdal/win32/1.6/gdalwin32exe160.zip Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
RE: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Phil, Thanks for the suggestion. I suspect it will work. My XP SP3 machine has VC90 entries in C:\Windows\WinSxS, while my Vista SP1 machine does not. But if GDAL requires the user to install the VC++ redistributable first, why is GDAL redisting the DLLs (e.g. msvcr90.dll) in the GDAL\bin directory? I suspect the intent was to override sxs in the build process, or specify a publisher policy, or something, so that the user does not have to install the redistributable themselves. The idea being that GDAL would work like old-school, pre-sxs applications, where you just have to have the right DLL versions in the same directory as your .exe. Was that not the intent? Are users indeed expected to install that redistributable first? Thanks, Jason -Original Message- From: Philippe Vachon [mailto:phili...@cowpig.ca] Sent: Monday, December 15, 2008 5:41 PM To: Jason Roberts Cc: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista? Hi Jason, I just tried to reproduce this, but wasn't able to; perhaps you don't have the latest version of the C Runtimes installed. It looks as though GEOS_C.DLL has correct manifest data embedded for the VC90 runtime (Visual Studio 2008) so as long as you have the correct assembly installed for MSVC it should run. I believe installing the redistributable components (http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7 -A40D-3802B2AF5FC2&displaylang=en) should be sufficient to get the proper versions of the assemblies installed. Cheers, Phil On Mon, Dec 15, 2008 at 05:12:02PM -0500, Jason Roberts wrote: >Greetings GDAL developers, > > > >I cannot get GDAL 1.6.0 to work on Windows Vista SP1. It appears that >there is a DLL Hell problem that does not appear on XP SP3, at least with >my machines. > > > >Repro steps on Vista SP1: > > > >1.Download >ftp://ftp.remotesensing.org/gdal/win32/1.6/gdalwin32exe160.zip and >decompress to C:\gdalwin32-1.6 > >2.From cmd.exe shell: > >a.SET PATH=C:\gdalwin32-1.6\bin;%PATH% > >b.SET GDAL_DATA=C:\gdalwin32-1.6\data > >c.C:\gdalwin32-1.6\bin\gdalinfo.exe > >3.Receive the following dialog box: > > > >--- > >gdalinfo.exe - Application Error > >--- > >The application failed to initialize properly (0xc0150002). Click OK to >terminate the application. > >--- > >OK > >--- > > > >The event log contains a new event: Source = SideBySide, Event ID = 33, >Description = Activation context generation failed for >"C:\gdalwin32-1.6\bin\geos_c.dll". Dependent Assembly > Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18 e3b",type="win32",version="9.0.21022.8" >could not be found. Please use sxstrace.exe for detailed diagnosis. > > > >Running depends.exe on C:\gdalwin32-1.6\bin\geos_c.dll gives the error " >Error: The Side-by-Side configuration information for >"c:\gdalwin32-1.6\bin\GEOS_C.DLL" contains errors. The application has >failed to start because its side-by-side configuration is incorrect. >Please see the application event log for more detail (14001)." Looking in >the event log again, we have another instance of the event above. > > > >This looks like a classic DLL Hell problem, with Vista thrown in just to >make it more confusing. Please let me know if I've somehow messed up the >install or am missing something obvious. Apologies if I am... > > > >I will investigate a bit further, but not being a GDAL developer, I do not >know which compilers you use, how you intend to link to MSVCRT, etc. If >the GDAL "build guy" could look at this, I'd really appreciate it. If you >send private builds, I can try them out with quick turnaround. > > > >Thanks for your help, > > > >Jason > > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Hi Jason, I just tried to reproduce this, but wasn't able to; perhaps you don't have the latest version of the C Runtimes installed. It looks as though GEOS_C.DLL has correct manifest data embedded for the VC90 runtime (Visual Studio 2008) so as long as you have the correct assembly installed for MSVC it should run. I believe installing the redistributable components (http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en) should be sufficient to get the proper versions of the assemblies installed. Cheers, Phil On Mon, Dec 15, 2008 at 05:12:02PM -0500, Jason Roberts wrote: >Greetings GDAL developers, > > > >I cannot get GDAL 1.6.0 to work on Windows Vista SP1. It appears that >there is a DLL Hell problem that does not appear on XP SP3, at least with >my machines. > > > >Repro steps on Vista SP1: > > > >1.Download >ftp://ftp.remotesensing.org/gdal/win32/1.6/gdalwin32exe160.zip and >decompress to C:\gdalwin32-1.6 > >2.From cmd.exe shell: > >a.SET PATH=C:\gdalwin32-1.6\bin;%PATH% > >b.SET GDAL_DATA=C:\gdalwin32-1.6\data > >c.C:\gdalwin32-1.6\bin\gdalinfo.exe > >3.Receive the following dialog box: > > > >--- > >gdalinfo.exe - Application Error > >--- > >The application failed to initialize properly (0xc0150002). Click OK to >terminate the application. > >--- > >OK > >--- > > > >The event log contains a new event: Source = SideBySide, Event ID = 33, >Description = Activation context generation failed for >"C:\gdalwin32-1.6\bin\geos_c.dll". Dependent Assembly > > Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" >could not be found. Please use sxstrace.exe for detailed diagnosis. > > > >Running depends.exe on C:\gdalwin32-1.6\bin\geos_c.dll gives the error " >Error: The Side-by-Side configuration information for >"c:\gdalwin32-1.6\bin\GEOS_C.DLL" contains errors. The application has >failed to start because its side-by-side configuration is incorrect. >Please see the application event log for more detail (14001)." Looking in >the event log again, we have another instance of the event above. > > > >This looks like a classic DLL Hell problem, with Vista thrown in just to >make it more confusing. Please let me know if I've somehow messed up the >install or am missing something obvious. Apologies if I am... > > > >I will investigate a bit further, but not being a GDAL developer, I do not >know which compilers you use, how you intend to link to MSVCRT, etc. If >the GDAL "build guy" could look at this, I'd really appreciate it. If you >send private builds, I can try them out with quick turnaround. > > > >Thanks for your help, > > > >Jason > > > ___ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
RE: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
FYI, here is the output from running sxstrace.exe and attempting to execute gdalinfo.exe. I haven't tried to determine what this means yet. (At first glance, I am wondering why Windows is trying to probe for .NET assemblies in the first place, since I expected that GDAL would not contain any. But then this is Vista, so all bets are off.) = Begin Activation Context Generation. Input Parameter: Flags = 0 ProcessorArchitecture = x86 CultureFallBacks = en-US;en ManifestPath = C:\gdalwin32-1.6\bin\geos_c.dll AssemblyDirectory = C:\gdalwin32-1.6\bin\ Application Config File = - INFO: Parsing Manifest File C:\gdalwin32-1.6\bin\geos_c.dll. INFO: Manifest Definition Identity is (null). INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18 e3b",type="win32",version="9.0.21022.8" INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18 e3b",type="win32",version="9.0.21022.8". INFO: Resolving reference for ProcessorArchitecture x86. INFO: Resolving reference for culture Neutral. INFO: Applying Binding Policy. INFO: No publisher policy found. INFO: No binding policy redirect found. INFO: Begin assembly probing. INFO: Did not find the assembly in WinSxS. INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.CRT\9.0.21022.8__1fc8b3b9a1e18e3b\ Microsoft.VC90.CRT.DLL. INFO: Attempt to probe manifest at C:\gdalwin32-1.6\bin\Microsoft.VC90.CRT.DLL. INFO: Attempt to probe manifest at C:\gdalwin32-1.6\bin\Microsoft.VC90.CRT.MANIFEST. INFO: Attempt to probe manifest at C:\gdalwin32-1.6\bin\Microsoft.VC90.CRT\Microsoft.VC90.CRT.DLL. INFO: Attempt to probe manifest at C:\gdalwin32-1.6\bin\Microsoft.VC90.CRT\Microsoft.VC90.CRT.MANIFEST. INFO: Did not find manifest for culture Neutral. INFO: End assembly probing. ERROR: Cannot resolve reference Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18 e3b",type="win32",version="9.0.21022.8". ERROR: Activation Context generation failed. End Activation Context Generation. From: gdal-dev-boun...@lists.osgeo.org [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Jason Roberts Sent: Monday, December 15, 2008 5:12 PM To: gdal-dev@lists.osgeo.org Subject: [gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista? Greetings GDAL developers, I cannot get GDAL 1.6.0 to work on Windows Vista SP1. It appears that there is a DLL Hell problem that does not appear on XP SP3, at least with my machines. Repro steps on Vista SP1: 1.Download ftp://ftp.remotesensing.org/gdal/win32/1.6/gdalwin32exe160.zip and decompress to C:\gdalwin32-1.6 2.From cmd.exe shell: a.SET PATH=C:\gdalwin32-1.6\bin;%PATH% b.SET GDAL_DATA=C:\gdalwin32-1.6\data c.C:\gdalwin32-1.6\bin\gdalinfo.exe 3.Receive the following dialog box: --- gdalinfo.exe - Application Error --- The application failed to initialize properly (0xc0150002). Click OK to terminate the application. --- OK --- The event log contains a new event: Source = SideBySide, Event ID = 33, Description = Activation context generation failed for "C:\gdalwin32-1.6\bin\geos_c.dll". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18 e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis. Running depends.exe on C:\gdalwin32-1.6\bin\geos_c.dll gives the error " Error: The Side-by-Side configuration information for "c:\gdalwin32-1.6\bin\GEOS_C.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail (14001)." Looking in the event log again, we have another instance of the event above. This looks like a classic DLL Hell problem, with Vista thrown in just to make it more confusing. Please let me know if I've somehow messed up the install or am missing something obvious. Apologies if I am. I will investigate a bit further, but not being a GDAL developer, I do not know which compilers you use, how you intend to link to MSVCRT, etc. If the GDAL "build guy" could look at this, I'd really appreciate it. If you send private builds, I can try them out with quick turnaround. Thanks for your help, Jason ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
[gdal-dev] GDAL 1.6.0 DLL Hell problem on Windows Vista?
Greetings GDAL developers, I cannot get GDAL 1.6.0 to work on Windows Vista SP1. It appears that there is a DLL Hell problem that does not appear on XP SP3, at least with my machines. Repro steps on Vista SP1: 1.Download ftp://ftp.remotesensing.org/gdal/win32/1.6/gdalwin32exe160.zip and decompress to C:\gdalwin32-1.6 2.From cmd.exe shell: a.SET PATH=C:\gdalwin32-1.6\bin;%PATH% b.SET GDAL_DATA=C:\gdalwin32-1.6\data c.C:\gdalwin32-1.6\bin\gdalinfo.exe 3.Receive the following dialog box: --- gdalinfo.exe - Application Error --- The application failed to initialize properly (0xc0150002). Click OK to terminate the application. --- OK --- The event log contains a new event: Source = SideBySide, Event ID = 33, Description = Activation context generation failed for "C:\gdalwin32-1.6\bin\geos_c.dll". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18 e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis. Running depends.exe on C:\gdalwin32-1.6\bin\geos_c.dll gives the error " Error: The Side-by-Side configuration information for "c:\gdalwin32-1.6\bin\GEOS_C.DLL" contains errors. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail (14001)." Looking in the event log again, we have another instance of the event above. This looks like a classic DLL Hell problem, with Vista thrown in just to make it more confusing. Please let me know if I've somehow messed up the install or am missing something obvious. Apologies if I am. I will investigate a bit further, but not being a GDAL developer, I do not know which compilers you use, how you intend to link to MSVCRT, etc. If the GDAL "build guy" could look at this, I'd really appreciate it. If you send private builds, I can try them out with quick turnaround. Thanks for your help, Jason ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
