qgis 2.12 does not compile

[aaschwanden (Andy Aschwanden)]

Hi,

I've been trying to install the qgis 2.12 port both with and without the grass variants. Compilation fails in both cases, see attached main.log

Andy

[aaschwanden (Andy Aschwanden)]

I've isolated the error:

:info:build fatal: Not a git repository (or any of the parent directories): .git
:info:build [  0%] Building C object src/providers/grass/6/CMakeFiles/qgis.g.info6.dir/__/qgis.g.info.c.o
:info:build make[2]: *** [qgsversion.h] Error 128

which seems to be related to the following qgis bug:

​https://hub.qgis.org/issues/13680

Is there a way this can be patched?

[Veence (Vincent)]

I will have a look into this, but I can't figure out why I don't run into the same issue.

Besides, FYI, I almost have a working Grass7 port.

[aaschwanden (Andy Aschwanden)]

Replying to vince@…:

I will have a look into this, but I can't figure out why I don't run into the same issue.

Besides, FYI, I almost have a working Grass7 port.

Good question, I'm afraid I don't know why it works for you but not for me. QGIS now has a fast (4 month) release cycle, and the improvements I've seen since 2.2 are really awesome. On the other hand since 2.8 there have been issues that required patching and several bugs made into the release (I had to apply some patches to 2.10).

This makes me wonder: Would it be useful/feasible/desirable to have two ports, a 'qgis' port and a 'qgis-dev' port. The 'qgis' port would always be the LTR (currently 2.8), while the 'qgis-dev' release would upgrade to every major versions (2.12, 2.14, etc...). This way, users with a desire for stability have their port while users how want to use the latest features have their own port.

[Veence (Vincent)]

Somebody else has the same problem. I wonder where that comes from. Going to look into this tomorrow.

[Veence (Vincent)]

Which version of Cmake have you installed?

[aaschwanden (Andy Aschwanden)]

3.4.0

$ port installed cmake
The following ports are currently installed:
  cmake @3.3.2_1
  cmake @3.4.0_0 (active)

[Veence (Vincent)]

Ok. Thanks. I'll investigate further, but it seems to be a recurring bug (if Google serves).

[garethsimons@…]

Replying to andy.aschwanden@…:

This makes me wonder: Would it be useful/feasible/desirable to have two ports, a 'qgis' port and a 'qgis-dev' port. The 'qgis' port would always be the LTR (currently 2.8), while the 'qgis-dev' release would upgrade to every major versions (2.12, 2.14, etc...). This way, users with a desire for stability have their port while users how want to use the latest features have their own port.

This would be nice. e.g. at the moment with 2.12 not working for me it would be nice to fall back on another version.

[Veence (Vincent)]

I have committed a simple patch in r142895. Please update and try again.

[aaschwanden (Andy Aschwanden)]

Replying to vince@…:

I have committed a simple patch in r142895. Please update and try again.

Compiles and runs for me. I haven't had a chance to test the Grass7 bindings yet.

Thanks for the fix!

[Veence (Vincent)]

Great! I was convinced it had something to do with this. By chance, do you have the Macports version of GIT installed?

[aaschwanden (Andy Aschwanden)]

Thanks very much. Yes I have git installed via Macports:

$ port installed git
The following ports are currently installed:
  git @2.6.2_0+bash_completion+credential_osxkeychain+doc+pcre+perl5_16+python27+svn
  git @2.6.2_1+bash_completion+credential_osxkeychain+doc+pcre+perl5_16+python27+svn (active)

[Veence (Vincent)]

I was pretty sure you had. The configure script detects your macports git, whereas it does not detect the system provided git (assuming it exists). The patch I wrote just overrides the detection and pretends there is no application to handle .git files.

Thanks for looking into this!