[GRASS5] discussion on how to package binaries

Markus Neteler neteler at itc.it
Mon Mar 8 12:01:37 EST 2004

On Sat, Mar 06, 2004 at 07:09:14PM +0000, Paul Kelly wrote:
> Glynn Clements wrote:
> > 
> > Scott Mitchell wrote:
> > 
> [...]
> > >
> > > Then, I went back and reconfigured without --enable-shared, did a make
> > > pre-compile and recompiled r.[in,out].png, and "r.tiff", then re-did
> > > gmakelinks, make install-strip, and make bindist.  I thought that would
> > > create binaries with everything compiled in for those particular
> > > import/export routines.  Apparently I misunderstand still, because the
> > > resulting programs are still looking for the right .dylib files.
> > 
> > --enable-shared controls whether the GRASS libraries (libgis,
> > libraster etc) are built as shared libraries. It has no effect upon
> > which external libraries are used.
> > 
> and --enable-shared is only effective if the alternate build system is
> being used, i.e. --enable-gmake=no has also been specified. In fact
> --enable-shared is the default so there is no need to specify it; it
> simply has no effect with --enable-gmake=yes as the traditional gmake
> build system doesn't support shared libraries.
> The logic of the --enable-shared and --enable-gmake switches could
> definitely be changed or improved as Hamish suggested recently. I would
> want to wait for a consensus before changing it however, especially as
> the current logic made good sense to me at the time I implemented it.

I suggest to make --enable-shared etc the default.
It works smoothly on the known platforms, only with such a change
we'll find the platforms with problems.


More information about the grass-dev mailing list