[GRASS-dev] GRASS module version strictness (libgrass_gis)

[Jürgen E. Fischer]

Hi,

On Fri, 05. Mar 2021 at 20:23:47 +0100, Benjamin Ducke wrote:
> I am trying to find a way to inject GRASS modules (C code)
> compiled  in a GRASS 7 source tree into an already installed
> version of GRASS. Even if I compile in a GRASS 7.8.5 tree and
> then copy into a GRASS 7.8.5 (i.e. exact version match)
> installation, I get this:
> 
> ERROR: Module built against version 2021-03-04T21:51:47+00:00 but trying to
>        use version 2021-01-01T10:33:43+00:00. You need to rebuild GRASS GIS
>        or untangle multiple installations.
> 
> This is coming from 'libgrass_gis'.

> Apparently, GRASS keeps exact timestamps of the binaries and
> won't allow any mixing.

Note: In OSGeo4W testing I've disabled that check in lib/gis/gisinit.c.  The
DLLs already carry the major and minor version number in their name already.

I guess it's there because the ABI could change anytime - even in point
releases - and the libs are only meant for GRASS itself AFAIK.

But I'd also think that the chance for breakages is reasonable small enough to
do this.  Using the libs with a different compiler in the QGIS plugin like we
do is probably a bigger risk anyway.


Jürgena.

-- 
Jürgen E. Fischer           norBIT GmbH             Tel. +49-4931-918175-31
Dipl.-Inf. (FH)             Rheinstraße 13          Fax. +49-4931-918175-50
Software Engineer           D-26506 Norden            https://www.norbit.de
QGIS release manager (PSC)  Germany                    IRC: jef on FreeNode
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20210305/697719a1/attachment.sig>