On Thu, Apr 16, 2015 at 01:52:55PM +0300, Lubomir I. Ivanov wrote: > On 16 April 2015 at 01:29, Dirk Hohndel <[email protected]> wrote: > > Those of you building from source... if you haven't switched to cmake, > > yet, now would be a very good time. I'm planning to drop support for qmake > > fairly soon, so please give it a try and let me know if there are any > > issues. > > > > i was able to again hack my way trough the native win32 build. > it's tolerable, but the pkg-config issues have deepened. > > 1) > pkg_config_library(LIBGIT2 libgit2) > ^ this seems to require an extra argument for me (e.g. REQUIRED) > otherwise it fails.
Oops, missed that one in commit 7596db28b5ad Fix pushed. > 2) > FIND_PACKAGE(Libdivecomputer REQUIRED) > > ^ i have cloned the subsurface fork of libdc in a folder, but this > does not work for me. > can we allow optional: > pkg_config_library(LIBDIVECOMPUTER libdivecomputer REQUIRED) > > this means that the original libdc PC file points at the same folder. We have changed the way it finds things that you build from source. There is now an assumption built in that directories for those libraries are either parallel to your Subsurface source directory, or that you have an install-root directory parallel to the Subsurface source directory that you install into - take a look at build.sh > 3) > i think NO_MARBLE from the command line would be nice? > i hardly build subsurface with marble support anymore. Any reason why you don't build that anymore? It's one of the key features... or is it just to painful for native Windows builds? /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
