Maybe it is PYTHONPATH

BUT...

Python and the GUI is compiling and working just fine otherwise. And Python 
runs with no problem in the terminal.

The bogus errors for compiling mapswipe, composer, etc first appeared with what 
I think was the introduction of a new window class for these modules. I have 
not seen the toolbox, but it may reuse the same code. If I knew what this new 
code is, I might be able to troubleshoot it. But I don't have time to try to 
reverse engineer it without guidance as to where to look. The error on 
importing wx is misleading as to what the real error is.

I can't say for sure that these are all related (and the error is indeed 
somewhat different for the toolbox compilation). But it seems a reasonable 
place to start.

If it IS a PYTHONPATH problem, then the code for building the toolbox is 
somehow ignoring PYTHONPATH because this is set properly otherwise.

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

voice:  480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:          480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu











On Jun 7, 2013, at 5:20 AM, Anna Petrášová 
<[email protected]<mailto:[email protected]>>
 wrote:




On Thu, Jun 6, 2013 at 7:16 PM, Michael Barton 
<[email protected]<mailto:[email protected]>> wrote:
Anna,

This is from the log. It looks to me like a path problem during compilation

Traceback (most recent call last):
  File "tools/build_modules_xml.py", line 85, in <module>
    sys.exit(main())
  File "tools/build_modules_xml.py", line 77, in main
    header(fh)
  File "tools/build_modules_xml.py", line 58, in header
    import grass.script.core as grass
ImportError: No module named grass.script.core
make[1]: *** 
[/Users/Shared/grass_dev/grass7_dev/dist.x86_64-apple-darwin12.3.0/etc/gui/wxpython/xml/module_items.xml]
 Error 1
make: [default] Error 2 (ignored)
make xml/menudata.xml
make[1]: `xml/menudata.xml' is up to date.
make menustrings.py

The other bogus errors on "No module named wx" also seems like a path problem.

yes, problem might be in PYTHONPATH. Could you ask about this William? I have 
currently no time and I am probably not able to solve this.

Regards,

Anna


Michael
______________________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice:  480-965-6262<tel:480-965-6262> (SHESC), 480-727-9746<tel:480-727-9746> 
(CSDC)
fax:          480-965-7671<tel:480-965-7671>(SHESC), 
480-727-0709<tel:480-727-0709> (CSDC)
www:  http://csdc.asu.edu<http://csdc.asu.edu/>, 
http://shesc.asu.edu<http://shesc.asu.edu/>
http://www.public.asu.edu/~cmbarton

On Jun 6, 2013, at 2:39 AM, Anna Petrášová 
<[email protected]<mailto:[email protected]>> wrote:

Hi, Michael,


On Wed, Jun 5, 2013 at 11:45 PM, Michael Barton 
<[email protected]<mailto:[email protected]>> wrote:
OK. I did this remotely but hopefully it is what you need.

yes, perfect, thanks. Could you try the compilation again with the change 
William did recently (demolocation probem, [1])? It might be related because 
from the errors in the log it seems that the virtual grass session is not 
there. If the problem is still there, please send me updated compilation log.

Thanks,
Anna


[1] https://trac.osgeo.org/grass/changeset/56621




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

voice:  480-965-6262<tel:480-965-6262> (SHESC), 480-727-9746<tel:480-727-9746> 
(CSDC)
fax:          480-965-7671<tel:480-965-7671> (SHESC),  
480-727-0709<tel:480-727-0709> (CSDC)
www: http://www.public.asu.edu/~cmbarton, 
http://csdc.asu.edu<http://csdc.asu.edu/>











On Jun 5, 2013, at 2:22 PM, Anna Petrášová 
<[email protected]<mailto:[email protected]>>
 wrote:




On Wed, Jun 5, 2013 at 11:07 PM, Michael Barton 
<[email protected]<mailto:[email protected]>> wrote:
Are you looking for the entire output from make?

just the make you run from gui/wxpython


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

voice:  480-965-6262<tel:480-965-6262> (SHESC), 480-727-9746<tel:480-727-9746> 
(CSDC)
fax:          480-965-7671<tel:480-965-7671> (SHESC),  
480-727-0709<tel:480-727-0709> (CSDC)
www: http://www.public.asu.edu/~cmbarton, 
http://csdc.asu.edu<http://csdc.asu.edu/>











On Jun 5, 2013, at 1:56 PM, Anna Petrášová 
<[email protected]<mailto:[email protected]>>
 wrote:




On Wed, Jun 5, 2013 at 10:38 PM, Michael Barton 
<[email protected]<mailto:[email protected]>> wrote:
Is the makefile output saved somewhere? I'm not at my office computer, but can 
access it remotely.

redirecting to file like this:

make 1> log.txt 2>&1


While this workaround works for me, it doesn't help as much for all the people 
who use my binaries.

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

voice:  480-965-6262<tel:480-965-6262> (SHESC), 480-727-9746<tel:480-727-9746> 
(CSDC)
fax:          480-965-7671<tel:480-965-7671> (SHESC),  
480-727-0709<tel:480-727-0709> (CSDC)
www: http://www.public.asu.edu/~cmbarton, 
http://csdc.asu.edu<http://csdc.asu.edu/>











On Jun 5, 2013, at 1:35 PM, Anna Petrášová 
<[email protected]<mailto:[email protected]>>
 wrote:




On Wed, Jun 5, 2013 at 9:59 PM, Michael Barton 
<[email protected]<mailto:[email protected]>> wrote:
OK. We are getting somewhere.

If I cd to the ../gui/wxpython directory inside the GRASS-7.0.app and run 
python core/toolboxes.py > xml/menudata.xml, it appears to create the 
menudata.xml file

GRASS then launches fine. It continues to launch fine subsequently.

Hm, so the problem is probably in the Makefile. Could you send me the whole 
make output (after make distclean)? Unfortunately I have very limited 
understanding of makefile rules, I was glad I made it work on my computer. At 
least you can use grass7 with this workaround now.

Anna


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

voice:  480-965-6262<tel:480-965-6262> (SHESC), 480-727-9746<tel:480-727-9746> 
(CSDC)
fax:          480-965-7671<tel:480-965-7671> (SHESC),  
480-727-0709<tel:480-727-0709> (CSDC)
www: http://www.public.asu.edu/~cmbarton, 
http://csdc.asu.edu<http://csdc.asu.edu/>











On Jun 5, 2013, at 12:01 PM, Anna Petrášová 
<[email protected]<mailto:[email protected]>> wrote:


Hi,

On Wed, Jun 5, 2013 at 1:40 AM, Michael Barton 
<[email protected]<mailto:[email protected]>> wrote:
Anna,

Still crashes.

See below.

On Mon, May 13, 2013 at 11:51 PM, Michael Barton 
<[email protected]<mailto:[email protected]>> wrote:
Perhaps I discovered the problem. Both the distribution version (downloaded in 
the past hour) and (of course) the compiled version of menudata.xml are empty.

Yes, that's what I was thinking. Could you try to run this separately:

python core/toolboxes.py > xml/menudata.xml

I assumed that you want me to run this from the GRASS terminal prompt???

yes. Have you run this from gui/wxpython directory? At least xml directory must 
be there.


python core/toolboxes.py > xml/menudata.xml
bash: xml/menudata.xml: No such file or directory

It's strange that Massimo recently compiled grass7 (with wxpython 2.9, but it 
should not be related, no gui is actually involved in this problem) and he 
didn't complain about this (Massimo, is that right?).

Anna













_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to