R: [GRASS-dev] WinGRASS Plans

[marco.pasetti at alice.it]

Hi Glynn,
 
Thanks for the explanation.
Since we are talking about, why an interpretated language for the GUI and not, for example, QT-OpenSource (that is compiled, cross-platform, GPL and has also Python bindings)? It's not a critic, just curiosity ;-)
 
Marco
 
PS: I didn't ignore your last e-mail about locking on Win; I'm just waiting to finish the new MSYS environment and then work again on the GRASS code...
 

________________________________

Da: Glynn Clements [mailto:glynn at gclements.plus.com]
Inviato: ven 06/06/2008 3.19
A: marco.pasetti at alice.it
Cc: Michael Barton; grass-dev at lists.osgeo.org
Oggetto: Re: [GRASS-dev] WinGRASS Plans




Marco Pasetti wrote:

> > Maybe this is what you have in mind, but I think that the wx-config is
> > only
> > needed for compiling vdigit, not for using it.
>
> Good! sorry, confused: I always thought that Python was an interpreted
> language.

It is. But it also supports extension through binary modules
(libraries) written in e.g. C or C++.

> I don't know anything about the new vdigit: does it have some C or
> C++ code parts to be compiled in Python?

The vdigit module has a mixture of C++ and Python code. The C++ code
is compiled into a binary module (.so, .dll); you need to configure
with --with-wxwidgets, which needs wx-config to get the compilation
and linking switches for the C++ code.

--
Glynn Clements <glynn at gclements.plus.com>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-dev/attachments/20080606/59fe9b3b/attachment.html