Maybe William has this built into his bundling code. When I compile and then create a Mac binary, I specify which wx I am using by pointing to a specific wx_config. We then bundle all wxPython code into the binary *.app and GRASS uses that, whatever wx is on the user’s system. Perhaps you can’t do something similar in Linux.
Michael ______________________________ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Head, Graduate Faculty in Complex Adaptive Systems Science Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www: http://csdc.asu.edu, http://shesc.asu.edu http://www.public.asu.edu/~cmbarton On Oct 30, 2014, at 3:14 PM, Glynn Clements <gl...@gclements.plus.com> wrote: > > Michael Barton wrote: > >> At least for me, it is possible to have multiple versions of wx >> installed. The important thing is which you use when you compile >> GRASS�determined by the path to wx_config > > The only module which is affected by wx-config is > visualisation/wximgview (which has probably been superseded by > scripts/wxpyimgview). > > Anything written in Python will use the wxPython version found by the > Python import mechanism and the wxversion module. > > If the code doesn't use wxversion, it will use whichever version > site-packages/wx.pth refers to. > > -- > Glynn Clements <gl...@gclements.plus.com> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
