Opened 16 years ago

Closed 16 years ago

#231 closed defect (fixed)

unable to locate xerces-c_2_7.dll

Reported by: maphew Owned by: warmerdam
Priority: major Milestone:
Component: OSGeo4W Keywords: setup
Cc:

Description

After Express install, I get this popup error when typing gdalinfo (or any other utility) in the OSGeo4W shell:

gdalinfo.exe - Unable To Locate Component

This application has failed to start because xerces-c_2_7.dll was not found.
Re-installing the application may fix this problem.

This is a new computer with relatively little installed on it, aside from ArcGIS, Thunderbird, Firefox. Windows XP Professional x64, SP2. I selected only GDAL to install.

Attachments (1)

osgeo4w-setup_deps.png (14.6 KB ) - added by maphew 16 years ago.
screen shot of setup showing dependencies selected

Download all attachments as: .zip

Change History (4)

comment:1 by warmerdam, 16 years ago

Keywords: setup added
Owner: changed from osgeo4w-dev@… to warmerdam

Confirmed, the express install package selection does not actually select dependencies for some reason. I'll dig into this.

comment:2 by maphew, 16 years ago

Once one has used the Express install the way (that I've found) to get setup to recalulate the dependencies is to

  1. Run osgeo4w-setup.exe
  2. Select [Advanced]
  3. Press [Next] until you get to "Select Packages" (5 times)
  4. Press [View] until it shows "Up To Date"
  5. Click on the circular arrows in the "New" column until it says "1.5.0-3" (Current is 1.5.0-2.'Reinstall' and 'Keep' appear to just repeat what Express install did, and have no effect.)
  6. Verify dependencies have now been calculated by pressing [View] until it says "Partial". The packages list should now show a bunch of new items (see attached).
  7. Continue install with [Next].

by maphew, 16 years ago

Attachment: osgeo4w-setup_deps.png added

screen shot of setup showing dependencies selected

comment:3 by warmerdam, 16 years ago

Resolution: fixed
Status: newclosed

I believe I have now corrected this problem. The key seems to be to keep calling p.selectMissing() in ExpressPackageSetupPage::OnNext() until p.isMet() returns TRUE. The fix is committed in r1076.

Note: See TracTickets for help on using tickets.