[osgeo4w-dev] Re: [osgeo4w] #85: please make wx-config available

OSGeo4W trac_osgeo4w at osgeo.org
Fri May 8 07:40:10 EDT 2009

#85: please make wx-config available
Reporter:  hamish       |        Owner:  osgeo4w-dev at lists.osgeo.org
    Type:  enhancement  |       Status:  new                        
Priority:  major        |    Component:  Package                    
 Version:               |   Resolution:                             
Keywords:               |  
Comment (by jef):

 wxPython was packaged from the binaries available from the wxPython
 website.  So wxWidgets development files were not necessary to package

 I know that wxWidgets is needed for the GRASS wxGUI python extensions, but
 I wasn't able to find or build wxWidgets so that the wxGUI extension would
 actually work.  I tried the development binaries from the wxPython
 website, that were use to build wxPython and tried several own builds from
 different versions of MSVC.  I could get it compile and link fine, but I
 wouldn't run correctly.

 Python, wxPython & wxWidgets are build with MSVC without a shell, so
 there's not much point in creating a shell script that emits options, that
 MSVC doesn't use or need.   And even if it were created, it probably would
 emit options for MSVC that couldn't be used by MinGW anyway.

 I've added gdal-config to the mingw-libs.  That's a handcrafted script
 that outputs options for MinGW to use the MSVC build libraries.  Something
 like that could also be done for wxWidgets, but therefore one would first
 need to figure out which options would be needed to make it actually work.

 Another approach would be to rebuild wxWidgets and wxPython using MinGW
 for GRASS, but that might not work with the MSVC built python.

Ticket URL: <http://trac.osgeo.org/osgeo4w/ticket/85#comment:2>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer for the OSGeo stack.

More information about the osgeo4w-dev mailing list