map support, Marble and Mac

[Gilles Caulier]

I just checked. Marble is optional for digiKam. If dependency is not
resolved, all code relevant are not compiled...

But your request is more to Marble team. If something need to be improved
with OSX support (and Windows to bundle application), this must be done in
Marble, not in client applications.

Gilles

2016-12-26 17:09 GMT+01:00 René J.V. Bertin <rjvbertin at gmail.com>:

> On Monday December 26 2016 15:11:03 Gilles Caulier wrote:
>
> Hi Gilles, and happy belated 2016 to you too ;)
>
> >If i'm not too wrong, Marble cmake support has been completely re-written
> >from scratch and is now more flexible to bundle (OSX and Windows).
> >https://frinring.wordpress.com/2016/12/15/marble-in-your-
> cmake-or-qmake-based-project-now-more-easy/
>
> I don't see anything about OS X or MS Windows on that page and in fact the
> remark that this was already possible since 16.08 makes me a bit
> suspicious. My current MacPorts package provides Marble from 16.08.2, and I
> this is the patch to make it build for shared & shareable resources:
>
> https://github.com/RJVB/macstrop/blob/master/kf5/kf5-
> marble/files/patch-build-for-macports-16082.diff
>
> The principle is simple: unlink the installation mode from the platform
> tokens, and introduce an option with a default value that does depend on a
> platform token. Hardly more difficult to maintain, it just requires the
> goodwill to ask oneself if a new Mac-specific addition is purely related to
> the installation mode or to the platform.
>
> I'll admit that I didn't even try to build it in stock version, but making
> a standalone and thus *relocatable* Marble app bundle is by definition
> incompatible with sharing libMarble.
>
> My bad btw: I updated the RR on ReviewBoard once but forgot it was
> supposed to go on Phabricator... Guess that means I'll have to give it
> another try ...
>
> R.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/calligra-devel/attachments/20161226/37a2939e/attachment.htm>