[GRASS-dev] Build winGRASS with Python and wxPython

On Feb 27, 2008, at 5:30 AM, grass-dev-request@lists.osgeo.org wrote:

Date: Wed, 27 Feb 2008 11:58:58 +0100
From: <marco.pasetti@alice.it>
Subject: [GRASS-dev] Build winGRASS with Python and wxPython
To: <grass-dev@lists.osgeo.org>
Message-ID: <FBCMMO02t4SPh1qHxpE0002f966@FBCMMO02.fbc.local>
Content-Type: text/plain; charset="iso-8859-1"

Hi all,

I installed prebuilt binaries of Python 2.5.2 and wxPython2.8 (unicode-2.8.7.1-py25); GRASS configure help tells to specify python and wxpython config files... but I don't have those files! any suggestions?

There is a separate dev Windows package that you need to instal for wx-config. This has been a confusing issue for many of us. There is a dev package for Linux that is part of the normal group of installations that you can install or not. The same files are installed automatically in the Mac binary, but put in a different place than Linux puts them. I saw a link for a Windows dev package on the binary downloads page for wxPython and suppose that this where you get these files for Windows--though I don't know where Windows will put them.

That said, you don't need to install this unless you want to try to compile the new in-development digitizer. Most people are still having difficulty compiling this and I know that Martin is actively working on it. It would certainly be helpful to him if you wanted to try compiling the digitizer in Windows--but this isn't necessary to run the rest of the wxPython GUI.

I also had a problem trying to enable python in GDAL, because the distributed Windows installer of Python is built using Visual Studio, while GDAL (if built with MinGW) requires a MinGW built version of Python; this means that, if you want to enable Python bindings in GDAL, you'll need to build Python from source using MinGW.

You don't need to enable Python in GDAL to use the wxPython GUI. But perhaps you are trying to enable Python in GDAL for other reasons?

Michael

I hope that it will be not the same even in GRASS! :wink:

Thanks

Marco

Hi Michael,

There is a separate dev Windows package that you need to instal for wx-config

oh… I thought it must exist! :wink: but I still didn’t find it… I’ll look better…

That said, you don’t need to install this unless you want to try to
compile the new in-development digitizer. Most people are still
having difficulty compiling this and I know that Martin is actively
working on it. It would certainly be helpful to him if you wanted to
try compiling the digitizer in Windows–but this isn’t necessary to
run the rest of the wxPython GUI.

mhhh… confused! if I don’t have wx-config I cannot enable the new wxPython GUI! (configure fails)

You don’t need to enable Python in GDAL to use the wxPython GUI. But
perhaps you are trying to enable Python in GDAL for other reasons?

Yes, you’re right. I’m working on a new MSYS environment for GRASS, and I’m trying to build the most options as possible to let user work on and test them in WinGrass (even if I’m not personally able to use those options).

If you tell me what data GRASS Makefile needs from wx-config file, I could modify configure and Makefile in order to work without wx-config

Regards,

Marco


Da: Michael Barton per conto di Michael Barton
Inviato: mer 27/02/2008 16.10
A: marco.pasetti@alice.it; GRASS developers list
Oggetto: Re: [GRASS-dev] Build winGRASS with Python and wxPython

On Feb 27, 2008, at 5:30 AM, grass-dev-request@lists.osgeo.org wrote:

Date: Wed, 27 Feb 2008 11:58:58 +0100
From: marco.pasetti@alice.it
Subject: [GRASS-dev] Build winGRASS with Python and wxPython
To: grass-dev@lists.osgeo.org
Message-ID: FBCMMO02t4SPh1qHxpE0002f966@FBCMMO02.fbc.local
Content-Type: text/plain; charset=“iso-8859-1”

Hi all,

I installed prebuilt binaries of Python 2.5.2 and wxPython2.8
(unicode-2.8.7.1-py25); GRASS configure help tells to specify
python and wxpython config files… but I don’t have those files!
any suggestions?

There is a separate dev Windows package that you need to instal for
wx-config. This has been a confusing issue for many of us. There is a
dev package for Linux that is part of the normal group of
installations that you can install or not. The same files are
installed automatically in the Mac binary, but put in a different
place than Linux puts them. I saw a link for a Windows dev package on
the binary downloads page for wxPython and suppose that this where
you get these files for Windows–though I don’t know where Windows
will put them.

That said, you don’t need to install this unless you want to try to
compile the new in-development digitizer. Most people are still
having difficulty compiling this and I know that Martin is actively
working on it. It would certainly be helpful to him if you wanted to
try compiling the digitizer in Windows–but this isn’t necessary to
run the rest of the wxPython GUI.

I also had a problem trying to enable python in GDAL, because the
distributed Windows installer of Python is built using Visual
Studio, while GDAL (if built with MinGW) requires a MinGW built
version of Python; this means that, if you want to enable Python
bindings in GDAL, you’ll need to build Python from source using MinGW.

You don’t need to enable Python in GDAL to use the wxPython GUI. But
perhaps you are trying to enable Python in GDAL for other reasons?

Michael

I hope that it will be not the same even in GRASS! :wink:

Thanks

Marco

Ciao Marco,

2008/2/27, marco.pasetti@alice.it <marco.pasetti@alice.it>:
Michael:

>There is a separate dev Windows package that you need to instal for
wx-config

Marco:

oh... I thought it must exist! :wink: but I still didn't find it... I'll look
better...

Michael:

>That said, you don't need to install this unless you want to try to
>compile the new in-development digitizer. Most people are still
>having difficulty compiling this and I know that Martin is actively
>working on it. It would certainly be helpful to him if you wanted to
>try compiling the digitizer in Windows--but this isn't necessary to
>run the rest of the wxPython GUI.

Marco:

mhhh... confused! if I don't have wx-config I cannot enable the new wxPython
GUI! (configure fails)

--with-widgets (and --with-python/c++) doesn't influence wxPython GUI
itself only compiling digitizer component (gui/wxpython/vdigit).
Python scripts from gui/wxpython are copied to $GISBASE/etc/wxpython
regardless you compiled vdigit or not. Compilation of vdigit is not
straightforward on Linux machines (requires wxPseudoDC from wxPython),
seems to be not possible on Mac (AFAIU). I will try to find better
solution ASAP.

Michael:

>You don't need to enable Python in GDAL to use the wxPython GUI. But
>perhaps you are trying to enable Python in GDAL for other reasons?

Marco:

Yes, you're right. I'm working on a new MSYS environment for GRASS, and I'm
trying to build the most options as possible to let user work on and test
them in WinGrass (even if I'm not personally able to use those options).

If you tell me what data GRASS Makefile needs from wx-config file, I could
modify configure and Makefile in order to work without wx-config

Only gui/wxpython/vdigit/Makefile.

Martin

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

On Feb 27, 2008, at 8:28 AM, <marco.pasetti@alice.it> wrote:

Hi Michael,

There is a separate dev Windows package that you need to instal for wx-config

oh… I thought it must exist! :wink: but I still didn’t find it… I’ll look better…

It’s a little link at the bottom of the paragraph on installing the Windows binary.

That said, you don’t need to install this unless you want to try to
compile the new in-development digitizer. Most people are still
having difficulty compiling this and I know that Martin is actively
working on it. It would certainly be helpful to him if you wanted to
try compiling the digitizer in Windows–but this isn’t necessary to
run the rest of the wxPython GUI.

mhhh… confused! if I don’t have wx-config I cannot enable the new wxPython GUI! (configure fails)

Leave out the --with-wxwigets. This is only used for compiling vdigit. Or maybe put in --without-wxwidgets.

Or you can leave it in and just ignore the error compiling vdigit I think.

Martin??

You don’t need to enable Python in GDAL to use the wxPython GUI. But
perhaps you are trying to enable Python in GDAL for other reasons?

Yes, you’re right. I’m working on a new MSYS environment for GRASS, and I’m trying to build the most options as possible to let user work on and test them in WinGrass (even if I’m not personally able to use those options).

If you tell me what data GRASS Makefile needs from wx-config file, I could modify configure and Makefile in order to work without wx-config

I don’t think this is necessary.

Michael

Regards,

Marco


Da: Michael Barton per conto di Michael Barton
Inviato: mer 27/02/2008 16.10
A: marco.pasetti@alice.it; GRASS developers list
Oggetto: Re: [GRASS-dev] Build winGRASS with Python and wxPython

On Feb 27, 2008, at 5:30 AM, grass-dev-request@lists.osgeo.org wrote:

Date: Wed, 27 Feb 2008 11:58:58 +0100
From: <marco.pasetti@alice.it>
Subject: [GRASS-dev] Build winGRASS with Python and wxPython
To: <grass-dev@lists.osgeo.org>
Message-ID: <FBCMMO02t4SPh1qHxpE0002f966@FBCMMO02.fbc.local>
Content-Type: text/plain; charset=“iso-8859-1”

Hi all,

I installed prebuilt binaries of Python 2.5.2 and wxPython2.8
(unicode-2.8.7.1-py25); GRASS configure help tells to specify
python and wxpython config files… but I don’t have those files!
any suggestions?

There is a separate dev Windows package that you need to instal for
wx-config. This has been a confusing issue for many of us. There is a
dev package for Linux that is part of the normal group of
installations that you can install or not. The same files are
installed automatically in the Mac binary, but put in a different
place than Linux puts them. I saw a link for a Windows dev package on
the binary downloads page for wxPython and suppose that this where
you get these files for Windows–though I don’t know where Windows
will put them.

That said, you don’t need to install this unless you want to try to
compile the new in-development digitizer. Most people are still
having difficulty compiling this and I know that Martin is actively
working on it. It would certainly be helpful to him if you wanted to
try compiling the digitizer in Windows–but this isn’t necessary to
run the rest of the wxPython GUI.

I also had a problem trying to enable python in GDAL, because the
distributed Windows installer of Python is built using Visual
Studio, while GDAL (if built with MinGW) requires a MinGW built
version of Python; this means that, if you want to enable Python
bindings in GDAL, you’ll need to build Python from source using MinGW.

You don’t need to enable Python in GDAL to use the wxPython GUI. But
perhaps you are trying to enable Python in GDAL for other reasons?

Michael

I hope that it will be not the same even in GRASS! :wink:

Thanks

Marco

On Feb 27, 2008, at 9:09 AM, Martin Landa wrote:

straightforward on Linux machines (requires wxPseudoDC from wxPython),
seems to be not possible on Mac (AFAIU). I will try to find better
solution ASAP.

Martin,

I DID find the wxWidgets code for Mac. It IS installed, just in a different place. However, there were other problems and Glynn indicated that make should be handled a different way for __libgdi.so. (probably I spelled this wrong from memory)

Hope this helps

Michael

Michael Barton wrote:

> mhhh... confused! if I don't have wx-config I cannot enable the new
> wxPython GUI! (configure fails)

Leave out the --with-wxwigets. This is only used for compiling vdigit.
Or maybe put in --without-wxwidgets.

Or you can leave it in and just ignore the error compiling vdigit I
think.

The vdigit directory is processed using the same rules as for module
directories. If there is an error building that directory, a line will
be added to the error.log file, but the rest of gui/wxpython will be
processed as normal.

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