Previously, we needed to set this path to compile GRASS so that it worked with wxPython wrappers for wxWidgets. I will do a new compile without this argument and see what happens.
In any case, I need to be able to make sure that GRASS uses the wxPython that is bundled with it by default to avoid differences in versions and SIP issues. 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 voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Jul 28, 2017, at 7:56 AM, Vaclav Petras <wenzesl...@gmail.com<mailto:wenzesl...@gmail.com>> wrote: On Thu, Jul 27, 2017 at 11:52 PM, Michael Barton <michael.bar...@asu.edu<mailto:michael.bar...@asu.edu>> wrote: > > The other issue I'm hitting is that the configure argument to enable > wxPython, '-with-wxwidgets=' expects a path to a wx_config file. AFAICT, > wxPython 4 does not have such a file. And I can't yet find anything that > seems to serve the same function. I can put in a path to the folder/directory > where the wxPython 4 files live. While this compiles without error, I don't > think it is using wxPython 4. > --with-wxwidgets= is for wxWidgets (C++ library), not wxPython (its Python wrapper), so you don't need to use at all. wxPython must be part of the Python installation you are using.
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
