[GRASS-dev] Re: [GRASS GIS] #61: vdigit makefile uses hardwired compile and link flags

GRASS GIS trac at osgeo.org
Mon Mar 24 13:47:32 EDT 2008

#61: vdigit makefile uses hardwired compile and link flags
  Reporter:  kyngchaos  |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect     |      Status:  new                      
  Priority:  major      |   Milestone:  6.4.0                    
 Component:  Python     |     Version:  6.3.0 RCs                
Resolution:             |    Keywords:                           
Comment (by glynn):

 Replying to [comment:8 kyngchaos]:
 > There is distutils.  Build it with distutils, and it will be compiled
 and linked correctly for each platform.  The problem with this is that it
 builds locally into a folder with a platform-specific name chosen by
 distutils (ie build/lib.macosx-10.5-i386-2.5), so the makefile would not
 know where it is to install it in the GRASS dist folder.  But it looks
 like there are build options to force a build dir name, so it would
 something known to the makefile.

 There are other Makefile integration issues, e.g. specifying the compiler,
 compilation switches, etc. Also, we don't want to re-compile files which
 haven't changed; that could become a significant issue for developers as
 the code grows.

 More generally, I don't like the idea of invoking commands where no-one
 understands what's going on under the hood (this is why we don't use
 libtool). And, AFAIK, no-one here understands the internals of distutils.

 If there is some way to get distutils to tell us which flags we should use
 (i.e. act like a working version of python-config), that would be

 Also, as it stands, we currently don't know how to invoke Python on the
 setup.py file (configure currently detects python-config, not python).

Ticket URL: <http://trac.osgeo.org/grass/ticket/61#comment:9>
GRASS GIS <http://grass.osgeo.org>
GRASS Geographic Information System (GRASS GIS) - http://grass.osgeo.org/

More information about the grass-dev mailing list