[GRASS-dev] Re: [GRASS GIS] #1125: wingrass - ctypes - compiling error

[GRASS GIS]

#1125: wingrass - ctypes - compiling error
------------------------------+---------------------------------------------
 Reporter:  hellik            |       Owner:  grass-dev@…              
     Type:  defect            |      Status:  new                      
 Priority:  blocker           |   Milestone:  6.5.0                    
Component:  Compiling         |     Version:  svn-trunk                
 Keywords:  wingrass, ctypes  |    Platform:  MSWindows Vista          
      Cpu:  x86-32            |  
------------------------------+---------------------------------------------

Comment(by glynn):

 Replying to [comment:24 hellik]:

 > What I have done now for testing of r43120 and r43121 in the osgeo4w-
 stack in WinVista32 is (I hope it's right the way?), is revert r43132

 Right; r43132 is bogus. The fact that ctypes generates errors is no reason
 to disable it. Errors in ctypes shouldn't prevent anything else from
 working (if it causes problems for the wxGUI, the bug is that wxnviz is
 part of the wxGUI process rather than a separate program).

 > and try if there are compiling errors.
 >
 {{{
 Errors in:
 No errors detected.
 }}}

 Good.

 > but as far as I can remember (correctly?), wx-nviz (3d-view-mode) is
 disabled at the moment in the WinGrass70-wxgui if a windows-platform is
 recognized.
 >
 {{{
 3D view mode not available
 Reason: No module named lib.grass
 }}}

 This error occurs if the ctypes wrappers didn't get built. Specifically,
 it indicates that:
 {{{
 from grass.lib.grass import *
 }}}
 failed.

 > what have I to do that I can test if - after Glynn's fixes with r43120
 and r43121 - the wx-nviz-module is working in WinGrass7 after no compiling
 errors?

 First, check that the $GISBASE/etc/python/grass/lib/*.py files exist. If
 not, check the build output relating to lib/python/ctypes.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1125#comment:25>
GRASS GIS <http://grass.osgeo.org>