Paul Kelly wrote: > >>> current trunk ./configure --help says that --with-python will enable > >>> Python support (Python bindings?). > >> > >> Yes. > >> > >>> Still I don't see any switch to enable/disable wxpython. Shouldn't > >>> there be one? > >> > >> It isn't needed. The Tcl/Tk and Python checks in gui/Makefile are both > >> bogus; those directories should be processed regardless of whether or > >> not Tcl/Tk or Python are installed on the build system. > > > > now gui/Makefile checks for wxPython instead of Python. wxPython stuff > > is installed only if --with-wxpython is given. > > I think Glynn's point was that the installation should simply be > unconditional with no checks in gui/Makefile - the wxPython stuff is just > scripts and doesn't need Python to be installed on the compilation system > for the scripts to be processed in any way (unlike C compiling) - the > requirement for wxPython is only on the system that GRASS is run on so it > should be a runtime check rather than a comile-time check.
Exactly. If you're cross-compiling e.g. building a Windows version on a Linux system, you shouldn't need to have a Windows version of Python/wxPython installed on the build system. Configure checks identify the compilation environment, not the run-time environment. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
