[Trillian] What are you supposed to do WITH a maniacally depressed robot?
[Marvin] You think you have problems? What are you supposed to do if you ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer...
[Trillian] What are you supposed to do WITH a maniacally depressed
robot?
[Marvin] You think you have problems? What are you supposed to do if
you ARE a maniacally depressed robot? No, don't try and answer, I'm
50,000 times more intelligent than you and even I don't know the
answer...
Hi,
current trunk ./configure --help says that --with-python will enable
Python support (Python bindings?). Still I don't see any switch to
enable/disable wxpython. Shouldn't there be one?
current trunk ./configure --help says that --with-python will enable
Python support (Python bindings?). Still I don't see any switch to
enable/disable wxpython. Shouldn't there be one?
yes, --wxpython is still missing. In my long-term TODO;-)
From what I could figure out about configure and make for GRASS Python:
--with-python enables wxpython. See gui/Makefile.
The swig bindings are manually built -- see the note in swig/makefile. And they don't appear to have any connection with --with-python.
On Jan 13, 2008, at 1:09 PM, Maris Nartiss wrote:
Hi,
current trunk ./configure --help says that --with-python will enable
Python support (Python bindings?). Still I don't see any switch to
enable/disable wxpython. Shouldn't there be one?
Which REQUIREMENTS.html document are you referring to?
For the wxPython GUI, you need Python 2.4 or greater and wxPython 2.8 or higher (maybe 2.8.1, but you might need to ask Martin on that).
Michael
____________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
[Trillian] What are you supposed to do WITH a maniacally depressed robot?
[Marvin] You think you have problems? What are you supposed to do if you ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer...
2008/1/13, William Kyngesburye <woklist@kyngchaos.com>:
From what I could figure out about configure and make for GRASS Python:
--with-python enables wxpython. See gui/Makefile.
The swig bindings are manually built -- see the note in swig/
makefile. And they don't appear to have any connection with --with-
python.
I added --with-wxpython option to configure script. wxPython requires
--with-python, also checks for python version >= 2.4 and wxpython >=
2.8.
Martin
On Jan 13, 2008, at 1:09 PM, Maris Nartiss wrote:
> Hi,
> current trunk ./configure --help says that --with-python will enable
> Python support (Python bindings?). Still I don't see any switch to
> enable/disable wxpython. Shouldn't there be one?
>
>
> Maris.
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.
The Tcl/Tk check is meant for code which links against the Tcl/Tk
libraries, namely NVIZ, v.digit and the form library.
> 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.
Martin
The Tcl/Tk check is meant for code which links against the Tcl/Tk
libraries, namely NVIZ, v.digit and the form library.
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.
Of course if the wxPython stuff does require Python on the compilation system, then what I've said is totally wrong...
>>> 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.