Re. subsurface: FTBFS in experimental

[Anton Lundin]

On 26 August, 2015 - Lutz Vieweg wrote:

> This thread has turned into a bitter fight over "distribution policies"
> vs. "upstream maintainer's freedom of choice", where I see valid arguments
> from both sides as well "too much emotion".
> 
> To contribute another view point:
> 
> I am using the most recent and up-to-date CentOS release, also on the
> laptop that I have with me to transfer dive data to, on boats on remote oceans.
> 
> Building Subsurface on CentOS from the sources has been very easy for
> versions up to 3.x.
> 
> Building Subsurface on CentOS has been somewhat cumbersome starting
> from version 4.0, due to lots of dependencies unavailable from the
> distribution, but was still done in an hour or so.
> 
> Yesterday I endeavored to build the Subsurface git master head on CentOS,
> and it was kind of a nightmare - everything, from just-one-patchlevel-version-of-
> cmake-ahead-of-what-CentOS-delivers, continuing with of course Qt 5 in a
> very certain version, and with lots of compile-time options to be tweaked,
> up the customized libgit/gmerlin/marble libraries had to be built from
> scratch, it took me ~50 attempts of error-spilling compiles until
> all the strange dependencies were finally resolved, resulting in a
> ~500MB sized installation directory.
> 
> After compiling, I wondered whether I should be happy about this success.
> Truth is, all the additions to Subsurface of the last 12 months or so
> are all about features I don't need/want/desire - like marble -
> or about things which I would rather like to have compile-time disabled - like
> the "cloud" and "social media" features/threats.
> 

There are a bunch of cmake flags to turn some bells off. Most of those
are to support different builds of subsurface, like the Android app, but
those can be (ab)used to "reduce" your subsurface building burden.

I use some of them in my local builds, but we STRONGLY recommend that
anyone not building subsurface for the own pleasure stay away from them.

A nother tip is to use Qt binaries from http://www.qt.io/ . Saves you
the hassle of building Qt. 


FBSUPPORT=OFF -> no more facebook share. Doesn't really add any overhead
but hey, if you're afraid of facebook, its gonski.

NO_MARBLE=ON -> don't link with marble, and don't display the marble
widget.


> But my frustration about the feature-creep induced inflation of the
> number of dependencies does _not_ cause me to share the "distribution policy
> should rule" standpoint.
> 

We try to provide a automatic build-script to remove as much hassle as
possible. scripts/build.sh is your friend.

If you find a way to make it make your life easier, patches are welcome =)


//Anton


-- 
Anton Lundin	+46702-161604