[GRASS-dev] WinGRASS Plans

GRASS GRASS developer
1

On 6/5/08 9:00 AM, "grass-dev-request@lists.osgeo.org"
<grass-dev-request@lists.osgeo.org> wrote:

In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read: compile
with wx for wx gui v.digit replacement
IIRC, to enable wxWidgets in the MSYS build we need a compiled (not prebuilt)
version of Python, but, at the moment, it's not possible to compile Python
under MSYS/MinGW. Is it (or will it be) strictly necessary to build the new
v.digit module?

You can get wxPython as an installable binary for Windows from the wxPython
site. No need to compile Python from source.

Mihcael
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

2

Hi Michael,

You can get wxPython as an installable binary for Windows from the wxPython
site. No need to compile Python from source.

yes, I know that (http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#wxPython), but I cannot enable the wxWidgets support (--with-wxwidgets=path/wx-config), because the wx-config file is available only if I built wxPython from source.

This said, I'm finishing the Vista build, but I need help for testings. Do you have some students *available* to make cross testings on both XP and Vista? I could test the build on Vista by myself, while on XP it's more difficult for me (I still have the old XP notebook, but I don't work at home, and I cannot keep 2 notebooks travelling..)

Thanks,

Marco

----- Original Message ----- From: "Michael Barton" <michael.barton@asu.edu>
To: <grass-dev@lists.osgeo.org>
Sent: Thursday, June 05, 2008 9:40 PM
Subject: Re: [GRASS-dev] WinGRASS Plans

On 6/5/08 9:00 AM, "grass-dev-request@lists.osgeo.org"
<grass-dev-request@lists.osgeo.org> wrote:

In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read: compile
with wx for wx gui v.digit replacement
IIRC, to enable wxWidgets in the MSYS build we need a compiled (not prebuilt)
version of Python, but, at the moment, it's not possible to compile Python
under MSYS/MinGW. Is it (or will it be) strictly necessary to build the new
v.digit module?

You can get wxPython as an installable binary for Windows from the wxPython
site. No need to compile Python from source.

Mihcael
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

3

Marco,

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. Also, I'm pretty sure that if
you install the Windows dev package, it has wx-config. Just trying to save
you some work.

I don't have anyone in my lab currently using Vista for testing. There will
be some students once we all come back for classes in mid-August.

Michael

On 6/5/08 12:59 PM, "Marco Pasetti" <marco.pasetti@alice.it> wrote:

Hi Michael,

You can get wxPython as an installable binary for Windows from the
wxPython
site. No need to compile Python from source.

yes, I know that
(http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#wxPython),
but I cannot enable the wxWidgets support (--with-wxwidgets=path/wx-config),
because the wx-config file is available only if I built wxPython from
source.

This said, I'm finishing the Vista build, but I need help for testings. Do
you have some students *available* to make cross testings on both XP and
Vista? I could test the build on Vista by myself, while on XP it's more
difficult for me (I still have the old XP notebook, but I don't work at
home, and I cannot keep 2 notebooks travelling..)

Thanks,

Marco

----- Original Message -----
From: "Michael Barton" <michael.barton@asu.edu>
To: <grass-dev@lists.osgeo.org>
Sent: Thursday, June 05, 2008 9:40 PM
Subject: Re: [GRASS-dev] WinGRASS Plans

On 6/5/08 9:00 AM, "grass-dev-request@lists.osgeo.org"
<grass-dev-request@lists.osgeo.org> wrote:

In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read:
compile
with wx for wx gui v.digit replacement
IIRC, to enable wxWidgets in the MSYS build we need a compiled (not
prebuilt)
version of Python, but, at the moment, it's not possible to compile
Python
under MSYS/MinGW. Is it (or will it be) strictly necessary to build the
new
v.digit module?

You can get wxPython as an installable binary for Windows from the
wxPython
site. No need to compile Python from source.

Mihcael
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
grass-dev Info Page

__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

4

Michael,

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. I don't know anything about the new vdigit: does it have some C or C++ code parts to be compiled in Python?

Also, I'm pretty sure that if
you install the Windows dev package, it has wx-config.

Windows dev package? I always used the *normal* installers; do you mean from here http://www.python.org/dev/daily-msi/?
BTW, I'm sure that the *normal* installer doesn't include the wx-config.

Just trying to save
you some work.

Thank you very much. I really appreciate that :wink:

I don't have anyone in my lab currently using Vista for testing. There will
be some students once we all come back for classes in mid-August.

OK. I'll try to do that with my XP notebook.

Thanks,

Marco

5

Michael,

Also, I'm pretty sure that if
you install the Windows dev package, it has wx-config.

I'm so stupid (or only tired?)!!

wxPython, obviously, not Python!

From the wxpython.org download page, Microsoft Windows section:

----------------------------------
If you have a need to compile other Python extension modules or applications that link with the same version of the wxWidgets DLL that wxPython does, then you will want to get the development package. It includes a snapshot of the wx headers and the import libraries found on my system when I made the wxPython binaries.

wxPython2.8-win32-devel
----------------------------------

I should download that package, right?

Marco

6

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@gclements.plus.com>

7

Yes. That's it.

Michael

On 6/5/08 4:54 PM, "Marco Pasetti" <marco.pasetti@alice.it> wrote:

Michael,

Also, I'm pretty sure that if
you install the Windows dev package, it has wx-config.

I'm so stupid (or only tired?)!!

wxPython, obviously, not Python!

From the wxpython.org download page, Microsoft Windows section:
----------------------------------
If you have a need to compile other Python extension modules or applications
that link with the same version of the wxWidgets DLL that wxPython does,
then you will want to get the development package. It includes a snapshot of
the wx headers and the import libraries found on my system when I made the
wxPython binaries.

wxPython2.8-win32-devel
----------------------------------

I should download that package, right?

Marco

__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

8

Marco,

2008/6/6 Marco Pasetti <marco.pasetti@alice.it>:

Michael,

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. I don't know anything about the new vdigit: does it have some C or
C++ code parts to be compiled in Python?

you need to compile Python extension (written in C++) located in
gui/wxpython/vdigit. Python just loads this extension when vector
digitizer is started.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

9

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 :wink:

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@gclements.plus.com]
Inviato: ven 06/06/2008 3.19
A: marco.pasetti@alice.it
Cc: Michael Barton; grass-dev@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@gclements.plus.com

10

Michael,

Yes. That’s it.

Perfect. Thanks :wink:

Just another thing: If I intended correctly, the dev is needed only for compile the C++ code in v.digit, while the normal release suffices to run it (since it has been compiled using the dev), right?

Marco

Da: Michael Barton [mailto:michael.barton@asu.edu]
Inviato: ven 06/06/2008 8.25
A: marco.pasetti@alice.it; grass-dev@lists.osgeo.org
Oggetto: Re: [GRASS-dev] WinGRASS Plans

Yes. That’s it.

Michael

On 6/5/08 4:54 PM, “Marco Pasetti” marco.pasetti@alice.it wrote:

Michael,

Also, I’m pretty sure that if
you install the Windows dev package, it has wx-config.

I’m so stupid (or only tired?)!!

wxPython, obviously, not Python!

From the wxpython.org download page, Microsoft Windows section:

If you have a need to compile other Python extension modules or applications
that link with the same version of the wxWidgets DLL that wxPython does,
then you will want to get the development package. It includes a snapshot of
the wx headers and the import libraries found on my system when I made the
wxPython binaries.

wxPython2.8-win32-devel

I should download that package, right?

Marco

Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

11

Michael,

sorry, forgot my last question; Martin already solved it.
Thanks

Marco

Da: grass-dev-bounces@lists.osgeo.org per conto di marco.pasetti@alice.it
Inviato: ven 06/06/2008 10.17
A: Michael Barton; grass-dev@lists.osgeo.org
Oggetto: R: [GRASS-dev] WinGRASS Plans

Michael,

Yes. That’s it.

Perfect. Thanks :wink:

Just another thing: If I intended correctly, the dev is needed only for compile the C++ code in v.digit, while the normal release suffices to run it (since it has been compiled using the dev), right?

Marco

Da: Michael Barton [mailto:michael.barton@asu.edu]
Inviato: ven 06/06/2008 8.25
A: marco.pasetti@alice.it; grass-dev@lists.osgeo.org
Oggetto: Re: [GRASS-dev] WinGRASS Plans

Yes. That’s it.

Michael

On 6/5/08 4:54 PM, “Marco Pasetti” marco.pasetti@alice.it wrote:

Michael,

Also, I’m pretty sure that if
you install the Windows dev package, it has wx-config.

I’m so stupid (or only tired?)!!

wxPython, obviously, not Python!

From the wxpython.org download page, Microsoft Windows section:

If you have a need to compile other Python extension modules or applications
that link with the same version of the wxWidgets DLL that wxPython does,
then you will want to get the development package. It includes a snapshot of
the wx headers and the import libraries found on my system when I made the
wxPython binaries.

wxPython2.8-win32-devel

I should download that package, right?

Marco

Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

12

marco.pasetti@alice.it wrote:

Since we are talking about, why an interpretated language for the GUI

It makes it easier for the user to customise the code, and to apply
updates.

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

13

Marco,

You can read the history of the discussions that led to wxPython on the GRASS WIKI.

Michael

On 6/6/08 1:04 AM, “marco.pasetti@alice.it” marco.pasetti@alice.it wrote:

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 :wink:

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@gclements.plus.com]
Inviato: ven 06/06/2008 3.19
A: marco.pasetti@alice.it
Cc: Michael Barton; grass-dev@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@gclements.plus.com

Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

14

Hy Glynn,

did you ever estimated the speed of the Python GUI Vs a generic compiled GUI?

On my old Notebook (AMD Athlon64 3000+, 1.25 GB RAM DDR, integrated NVIDIA GPU with shared 64 MB VRAM) I noticed that, very often, just opening a module GUI or a dialoge window caused the system to freeze for a while (XP Pro SP2, 32bit, very well maintained). This said, all the other GUI parts, such as the GIS Layer Manager and the Map Display, always worked very well, and never (maybe rarely) freezed.

Is that because the GUI is interpreted or is it only a Windows problem? actually, many Windows native application GUIs frequently freeze, even if they are compiled and not interpreted GUIs...

Thanks for your precious explanations, as always.. :slight_smile:

Marco

----- Original Message ----- From: "Glynn Clements" <glynn@gclements.plus.com>
To: <marco.pasetti@alice.it>
Cc: "Michael Barton" <michael.barton@asu.edu>; <grass-dev@lists.osgeo.org>
Sent: Friday, June 06, 2008 6:37 PM
Subject: Re: R: [GRASS-dev] WinGRASS Plans

marco.pasetti@alice.it wrote:

Since we are talking about, why an interpretated language for the GUI

It makes it easier for the user to customise the code, and to apply
updates.

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

15

Marco Pasetti wrote:

did you ever estimated the speed of the Python GUI Vs a generic compiled
GUI?

On my old Notebook (AMD Athlon64 3000+, 1.25 GB RAM DDR, integrated NVIDIA
GPU with shared 64 MB VRAM) I noticed that, very often, just opening a
module GUI or a dialoge window caused the system to freeze for a while (XP
Pro SP2, 32bit, very well maintained). This said, all the other GUI parts,
such as the GIS Layer Manager and the Map Display, always worked very well,
and never (maybe rarely) freezed.

Is that because the GUI is interpreted or is it only a Windows problem?
actually, many Windows native application GUIs frequently freeze, even if
they are compiled and not interpreted GUIs...

If you're talking about standalone GUIs (i.e. running a module from
the command-line with --ui, or with no arguments when it needs some),
that's probably the overhead of starting up the Python interpreter,
initialising the libraries, etc. I wouldn't expect that to be an issue
when creating dialogs from within the wxPython GUI.

In any case, using C/C++ for the GUI is a non-starter. The advantages
of being able to modify the code (whether for ongoing development or
for local customisations) without needing to re-compile everything far
outweigh any performance issues.

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

16

Hi Michael,

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. Also, I’m pretty sure that if
you install the Windows dev package, it has wx-config.

I downloaded the Windows dev package, but unfortunately it doesn’t contain the wx-config file; maybe because it has been built using MS Visual C++. I think I’ll need to build wxPython from source using MinGW to have the wx-config file and, thus, build the new GRASS v.digit.

I’ll let you know.

Regards,

Marco

17

Confirmed: no wx-config script in the Windows bin package :frowning:

However, before you go through the pain of building the whole
thing with MinGW: maybe try and snatch a copy of the wx-config script
from a Linux install, then just edit the variables in there
to fit your MinGW/MSYS setup?

Ben

marco.pasetti@alice.it wrote:

Hi Michael,
  >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. Also, I'm pretty sure that if
>you install the Windows dev package, it has wx-config.
I downloaded the Windows dev package, but unfortunately it doesn't contain the wx-config file; maybe because it has been built using MS Visual C++. I think I'll need to build wxPython from source using MinGW to have the wx-config file and, thus, build the new GRASS v.digit.
I'll let you know.
Regards,
Marco

------------------------------------------------------------------------

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

--
Benjamin Ducke
Senior Applications Support and Development Officer

Oxford Archaeological Unit Limited
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.

Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
benjamin.ducke@oxfordarch.co.uk

------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.

18

Hi Michael,

maybe try and snatch a copy of the wx-config script
from a Linux install, then just edit the variables in there
to fit your MinGW/MSYS setup?

yes! it could be a perfect soultion :slight_smile:

at the moment I suspended the wxWidgets support task for better times (I read the documentation… too much work and uncertain solutions for the moment…)
If the Linux script will woork … good! otherwise I will delay the task.

is there anyone outhere that could send me a linux wx-config script please? wxPython version is 2.8.7.1

Many thanks,

Marco

Da: grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
Inviato: gio 12/06/2008 13.24
Cc: grass-dev@lists.osgeo.org
Oggetto: Re: R: [GRASS-dev] WinGRASS Plans

Confirmed: no wx-config script in the Windows bin package :frowning:

However, before you go through the pain of building the whole
thing with MinGW: maybe try and snatch a copy of the wx-config script
from a Linux install, then just edit the variables in there
to fit your MinGW/MSYS setup?

Ben

marco.pasetti@alice.it wrote:

Hi Michael,

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. Also, I’m pretty sure
that if
you install the Windows dev package, it has wx-config.

I downloaded the Windows dev package, but unfortunately it doesn’t
contain the wx-config file; maybe because it has been built using MS
Visual C++. I think I’ll need to build wxPython from source using MinGW
to have the wx-config file and, thus, build the new GRASS v.digit.

I’ll let you know.

Regards,

Marco

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

–
Benjamin Ducke
Senior Applications Support and Development Officer

Oxford Archaeological Unit Limited
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.

Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
benjamin.ducke@oxfordarch.co.uk

Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

19

Here you go:

this one taken from 2.8.4.
But I really do not expect any major difference.
Just adjust the version number in the script ...

Ben

marco.pasetti@alice.it wrote:

Hi Michael,
  >maybe try and snatch a copy of the wx-config script
>from a Linux install, then just edit the variables in there
>to fit your MinGW/MSYS setup?
yes! it could be a perfect soultion :slight_smile:
at the moment I suspended the wxWidgets support task for better times (I read the documentation... too much work and uncertain solutions for the moment...)
If the Linux script will woork ... good! otherwise I will delay the task.
is there anyone outhere that could send me a linux wx-config script please? wxPython version is 2.8.7.1
Many thanks,
Marco

------------------------------------------------------------------------
*Da:* grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
*Inviato:* gio 12/06/2008 13.24
*Cc:* grass-dev@lists.osgeo.org
*Oggetto:* Re: R: [GRASS-dev] WinGRASS Plans

Confirmed: no wx-config script in the Windows bin package :frowning:

However, before you go through the pain of building the whole
thing with MinGW: maybe try and snatch a copy of the wx-config script
from a Linux install, then just edit the variables in there
to fit your MinGW/MSYS setup?

Ben

marco.pasetti@alice.it wrote:
> Hi Michael,
> > >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. Also, I'm pretty sure
> that if
> >you install the Windows dev package, it has wx-config.
> > I downloaded the Windows dev package, but unfortunately it doesn't
> contain the wx-config file; maybe because it has been built using MS
> Visual C++. I think I'll need to build wxPython from source using MinGW
> to have the wx-config file and, thus, build the new GRASS v.digit.
> > I'll let you know.
> > Regards,
> > Marco
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

--
Benjamin Ducke
Senior Applications Support and Development Officer

Oxford Archaeological Unit Limited
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.

Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
benjamin.ducke@oxfordarch.co.uk

------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info/&gt; for more information.

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

--
Benjamin Ducke
Senior Applications Support and Development Officer

Oxford Archaeological Unit Limited
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.

Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
benjamin.ducke@oxfordarch.co.uk

------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.

(attachments)

wx-config (41.1 KB)

20

Many thanks :slight_smile:

Marco

Da: Benjamin Ducke [mailto:benjamin.ducke@oxfordarch.co.uk]
Inviato: gio 12/06/2008 14.42
A: marco.pasetti@alice.it
Cc: grass-dev@lists.osgeo.org
Oggetto: Re: R: R: [GRASS-dev] WinGRASS Plans

Here you go:

this one taken from 2.8.4.
But I really do not expect any major difference.
Just adjust the version number in the script …

Ben

marco.pasetti@alice.it wrote:

Hi Michael,

maybe try and snatch a copy of the wx-config script
from a Linux install, then just edit the variables in there
to fit your MinGW/MSYS setup?

yes! it could be a perfect soultion :slight_smile:

at the moment I suspended the wxWidgets support task for better times (I
read the documentation… too much work and uncertain solutions for the
moment…)
If the Linux script will woork … good! otherwise I will delay the task.

is there anyone outhere that could send me a linux wx-config script
please? wxPython version is 2.8.7.1

Many thanks,

Marco

Da: grass-dev-bounces@lists.osgeo.org per conto di Benjamin Ducke
Inviato: gio 12/06/2008 13.24
Cc: grass-dev@lists.osgeo.org
Oggetto: Re: R: [GRASS-dev] WinGRASS Plans

Confirmed: no wx-config script in the Windows bin package :frowning:

However, before you go through the pain of building the whole
thing with MinGW: maybe try and snatch a copy of the wx-config script
from a Linux install, then just edit the variables in there
to fit your MinGW/MSYS setup?

Ben

marco.pasetti@alice.it wrote:

Hi Michael,

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. Also, I’m pretty sure
that if
you install the Windows dev package, it has wx-config.

I downloaded the Windows dev package, but unfortunately it doesn’t
contain the wx-config file; maybe because it has been built using MS
Visual C++. I think I’ll need to build wxPython from source using MinGW
to have the wx-config file and, thus, build the new GRASS v.digit.

I’ll let you know.

Regards,

Marco

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

–
Benjamin Ducke
Senior Applications Support and Development Officer

Oxford Archaeological Unit Limited
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.

Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
benjamin.ducke@oxfordarch.co.uk

Files attached to this email may be in ISO 26300 format (OASIS Open
Document Format). If you have difficulty opening them, please visit
http://iso26300.info <http://iso26300.info/> for more information.

grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

–
Benjamin Ducke
Senior Applications Support and Development Officer

Oxford Archaeological Unit Limited
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.

Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
benjamin.ducke@oxfordarch.co.uk

Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.