Re: [GRASS-dev] compilation success

2008-10-10 Thread William Kyngesburye
On Oct 9, 2008, at 9:36 PM, Glynn Clements wrote: William Kyngesburye wrote: To be honest, I'm not particularly confident of the OSX-specific rule for building the module: ifeq ($(findstring darwin,$(ARCH)),darwin) $(CXX) -o $@ $(LDFLAGS) $^ $(EXTRA_LIBS)

Re: [GRASS-dev] compilation success

2008-10-09 Thread William Kyngesburye
On Oct 9, 2008, at 4:38 AM, Glynn Clements wrote: Michael Barton wrote: With William's recent fix, I got farther tonight on getting a working wxPython nviz than ever before. I still have to remove render.c, but otherwise compilation goes well. When I select nviz from the map display, I now

Re: [GRASS-dev] compilation success

2008-10-09 Thread William Kyngesburye
On Oct 9, 2008, at 4:27 AM, Glynn Clements wrote: To be honest, I'm not particularly confident of the OSX-specific rule for building the module: ifeq ($(findstring darwin,$(ARCH)),darwin) $(CXX) -o $@ $(LDFLAGS) $^ $(EXTRA_LIBS) else I would expect that command

Re: [GRASS-dev] compilation success

2008-10-09 Thread Glynn Clements
Michael Barton wrote: Does init_grass6_wxnviz (or anything similar) show up in the output from: nm -D OBJ.*/_grass6_wxnviz.so ? I'm not sure I understand what you're asking. But here is a result. cmb-MBP-2:~ cmbarton$ cd /Applications/Grass/GRASS-6.4.app/Contents/

Re: [GRASS-dev] compilation success

2008-10-09 Thread Glynn Clements
Michael Barton wrote: With William's recent fix, I got farther tonight on getting a working wxPython nviz than ever before. I still have to remove render.c, but otherwise compilation goes well. When I select nviz from the map display, I now get a message box saying Please wait,

Re: [GRASS-dev] compilation success

2008-10-09 Thread Glynn Clements
William Kyngesburye wrote: To be honest, I'm not particularly confident of the OSX-specific rule for building the module: ifeq ($(findstring darwin,$(ARCH)),darwin) $(CXX) -o $@ $(LDFLAGS) $^ $(EXTRA_LIBS) else I would expect that command to try to build an

[GRASS-dev] compilation success

2008-10-08 Thread Michael Barton
I just updated GRASS 6.4 from the SVN and compiled. I had to compile the wxPython nviz and vdigit manually, but all compiled. This is very good news. The bad news is that neither vdigit nor nviz yet work. When I try vdigit, I still get a Unable to initialize display driver error. When I

Re: [GRASS-dev] compilation success

2008-10-08 Thread Glynn Clements
Michael Barton wrote: When I try the new nviz, I nothing happens visually, but I get the following in the layer manager output window. import grass6_wxnviz as wxnviz File /Applications/Grass/GRASS-6.4.app/Contents/MacOS/etc /wxpython/nviz/grass6_wxnviz.py, line 7, in module import

Re: [GRASS-dev] compilation success

2008-10-08 Thread William Kyngesburye
I updated wxpython/nviz/nviz.i - the #undef check fix from a while back was wrong, so it wouldn't compile. I haven't tried running it yet, I only have my brain half on this right now. But I ran into another interesting compile issue, that probably only a few would run into, when compiling

Re: [GRASS-dev] compilation success

2008-10-08 Thread Michael Barton
I'll try again. One of my students compiled GRASS 6.4 today on a PPC OSX 10.5 machine. It seemed to go well using native Python and new wxPython. Oddly (but fortunately) nviz (the old TclTk one) DOES seem to work fine with that. I'm not sure what is going on with mine. Are you compiling

Re: [GRASS-dev] compilation success

2008-10-08 Thread Michael Barton
With William's recent fix, I got farther tonight on getting a working wxPython nviz than ever before. I still have to remove render.c, but otherwise compilation goes well. When I select nviz from the map display, I now get a message box saying Please wait, loading data... and I get a