How to compile on trusty or xenial?

[probonopd]

Getting

CMake Error at /usr/local/cmake-3.12.4/share/cmake-3.12/Modules/FindBoost.cmake:2048 (message):
  Unable to find the requested Boost libraries.
  Boost version: 1.58.0
  Boost include path: /usr/include
  Detected version of Boost is too old.  Requested version was 1.60 (or
  newer).

How to compile on trusty or xenial?

References:

• https://github.com/probonopd/scantailor-advanced/blob/patch-1/.travis.yml
• https://travis-ci.com/probonopd/scantailor-advanced/builds/109090448

[derrikF]

https://github.com/4lex4/scantailor-libs-build#building-from-sources --> 6. Build boost:

[probonopd]

Thanks, I have managed to get it built using

sed -i -e 's|Boost 1.60|Boost 1.50|g' CMakeLists.txt

AppImages for testing:
https://github.com/probonopd/scantailor-advanced/releases

[probonopd]

Thanks. How can we get #60 merged @4lex4?

[4lex4]

I'll modify and merge that with develop branch later. Now that misses qt5 svg.

[probonopd]

Adding qt59svg to https://github.com/4lex4/scantailor-advanced/pull/60/files#diff-354f30a63fb0907d4ad57269548329e3R11 should do the trick.

[4lex4]

@probonopd the main issue is what your upload.sh will do with my release page (this part).
As you can see I work on the project in the develop branch and merge that with master only on releasing a new version.
And I don't want to break the releases structure by Continuous build on the top with the only asset which is the unversioned AppImage file (although this part I can fix myself by adding to the script extraction the version from version.h). As you can see my releases are tagged and contain version, changelog and assets containing, inter alia, binaries for windows. I need the AppImage file to be there along with the other assets and nothing more.

[probonopd]

As you can see I work on the project in the develop branch and merge that with master only on releasing a new version.

Where would you like continuous builds for the develop branch to be uploaded to?

[4lex4]

@probonopd, it could be any place but not the main release page, and I don't know whether github allows to show a release only for one branch and hide that for the others. Even if that does I'd like to make deploying on tagged builds for any branch anyway to provide Windows binaries along with AppImages: https://docs.travis-ci.com/user/deployment/releases/#deploying-only-on-tagged-builds

[probonopd]

You can build and upload for tagged builds only if you want, just replace my uploadtool calls with the native releases providers from Travis CI.

Nevertheless I personally find it very useful to always have a binary for every build (only the last successful build is kept).