A colleague is using a dev version of GRASS 7.2 installed on windows.
Trying to use a C-addon (r.object.geometry), he got an error about
version mismatch between the installed GRASS revision and the revision
of the GRASS base the addon was built against.
Does this message automatically appear when the revisions are
different, or only if relevant libraries have changed between the
revisions ? I imagine that the latter would not be easy, but does the
former really have to lead to a fatal error ?
On Wed, Sep 14, 2016 at 11:34 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
A colleague is using a dev version of GRASS 7.2 installed on windows.
Trying to use a C-addon (r.object.geometry), he got an error about
version mismatch between the installed GRASS revision and the revision
of the GRASS base the addon was built against.
Yes, because AFAIK the addons are built against 7.0.
With the ucoming release of 7.2. I expect that this will become the
base for addon compilation on Windows. But Martin will know more.
Does this message automatically appear when the revisions are
different, or only if relevant libraries have changed between the
revisions ? I imagine that the latter would not be easy, but does the
former really have to lead to a fatal error ?
On Wed, Sep 14, 2016 at 11:34 AM, Moritz Lennert
<
mlennert@.worldonline
> wrote:
A colleague is using a dev version of GRASS 7.2 installed on windows.
Trying to use a C-addon (r.object.geometry), he got an error about
version mismatch between the installed GRASS revision and the revision
of the GRASS base the addon was built against.
Yes, because AFAIK the addons are built against 7.0.
With the ucoming release of 7.2. I expect that this will become the
base for addon compilation on Windows. But Martin will know more.
Does this message automatically appear when the revisions are
different, or only if relevant libraries have changed between the
revisions ? I imagine that the latter would not be easy, but does the
former really have to lead to a fatal error ?
2016-09-14 11:49 GMT+02:00 Markus Neteler <neteler@osgeo.org>:
Yes, because AFAIK the addons are built against 7.0.
With the ucoming release of 7.2. I expect that this will become the
base for addon compilation on Windows. But Martin will know more.
Addons are built against different versions 7.0.x [1], 7.2.svn [2] and
7.3.svn [3].
Ma
PS: Unfortunately currently wingrass builds are completely broken.
Hope to have time to fix it today.
Le Wed, 14 Sep 2016 11:49:29 +0200,
Markus Neteler <neteler@osgeo.org> a écrit :
On Wed, Sep 14, 2016 at 11:34 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
> A colleague is using a dev version of GRASS 7.2 installed on
> windows. Trying to use a C-addon (r.object.geometry), he got an
> error about version mismatch between the installed GRASS revision
> and the revision of the GRASS base the addon was built against.
Yes, because AFAIK the addons are built against 7.0.
With the ucoming release of 7.2. I expect that this will become the
base for addon compilation on Windows. But Martin will know more.
AFAICT, addons are built daily for the daily builds of 7.2 and trunk:
> Does this message automatically appear when the revisions are
> different, or only if relevant libraries have changed between the
> revisions ? I imagine that the latter would not be easy, but does
> the former really have to lead to a fatal error ?
Le Wed, 14 Sep 2016 03:08:06 -0700 (PDT),
Helmut Kudrnovsky <hellik@web.de> a écrit :
Markus Neteler wrote
> On Wed, Sep 14, 2016 at 11:34 AM, Moritz Lennert
> <
> mlennert@.worldonline
> > wrote:
>> A colleague is using a dev version of GRASS 7.2 installed on
>> windows. Trying to use a C-addon (r.object.geometry), he got an
>> error about version mismatch between the installed GRASS revision
>> and the revision of the GRASS base the addon was built against.
>
> Yes, because AFAIK the addons are built against 7.0.
> With the ucoming release of 7.2. I expect that this will become the
> base for addon compilation on Windows. But Martin will know more.
>
>> Does this message automatically appear when the revisions are
>> different, or only if relevant libraries have changed between the
>> revisions ? I imagine that the latter would not be easy, but does
>> the former really have to lead to a fatal error ?
>
> The libraries changed between 7.0.x and 7.2.x (see
> https://trac.osgeo.org/grass/wiki/Release/7.2.0-News#Librarychanges).
> To my knowledge no binary compatibility is possible when it comes
> to C code.
>
> Markus
> _______________________________________________
> grass-dev mailing list
But there seems to be some compiling /building issues as there are no
dailies available.
Only for today. Yesterday, they were fine.
normally winGRASS addons are compiled against the correct revision.
That's what I thought. So the question remains: if the check only
blindly checks revision versions within the same branches, should this
be fatal ? Or maybe just a big fat warning...