Re: [QGIS-Developer] MacOS packaging current situation

[Tim Sutton]

Thanks for the update Peter. I probably can’t be much help with the actual 
packaging, but I am happy to help with testing etc.

Regards

Tim

> On 21 Feb 2020, at 08:47, Peter Petrik  
> wrote:
> 
> Hi, 
> 
> I would like to explain the current situation with the QGIS Mac Packaging on 
> Mac. The packager is dependent on the dependencies from 
> https://github.com/OSGeo/homebrew-osgeo4mac 
> , which were not updated to the 
> required proj6 versions yet. Last production-ready version was based on 
> GDAL2 and therefore the official all-in-one package is based on that too ATM. 
> The maintainers of homebrew-osgeo4mac work to update  to gdal3.04 and 
> proj6.3.1, but it will not be ready to today's release. 
> 
> I apologize for not fixing the packaging bugs for last few months, since I 
> was waiting for the gdal3 update first.
> 
> We are looking at how to solve this issue in the long term to be able to 
> update dependencies for QGIS versions more flexible and even use different 
> versions of libraries for PR, LTR and nightlies. I will look into various 
> options:
> 1. use (forked) homebrew for QGIS dependencies 
> 2. use conda for QGIS dependencies
> 3. compile deps ourselves, with a simple bash-based framework (like OSGeo4A)
> 
> If anyone is interested in helping with the packaging, we can do a meeting or 
> please send me a mail.
> 
> Kind regards,
> Peter
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—









Tim Sutton

Co-founder: Kartoza
Ex Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

I'd love to connect. Here's my calendar link  to 
make finding time easy.

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] MacOS packaging current situation

[Peter Petrik]

Hi,

I would like to explain the current situation with the QGIS Mac Packaging
on Mac. The packager is dependent on the dependencies from
https://github.com/OSGeo/homebrew-osgeo4mac, which were not updated to the
required proj6 versions yet. Last production-ready version was based
on GDAL2 and therefore the official all-in-one package is based on that too
ATM.
The maintainers of homebrew-osgeo4mac work to update  to gdal3.04 and
proj6.3.1, but it will not be ready to today's release.

I apologize for not fixing the packaging bugs for last few months, since I
was waiting for the gdal3 update first.

We are looking at how to solve this issue in the long term to be able to
update dependencies for QGIS versions more flexible and even use different
versions of libraries for PR, LTR and nightlies. I will look into various
options:
1. use (forked) homebrew for QGIS dependencies
2. use conda for QGIS dependencies
3. compile deps ourselves, with a simple bash-based framework (like OSGeo4A)

If anyone is interested in helping with the packaging, we can do a meeting
or please send me a mail.

Kind regards,
Peter
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Peter Petrik]

Hi,

thank you for all suggestions and feedback.

I think we managed to finish my small prototyping exercise for packaging.
We got Apple certificate for Lutra and Mac server on cloud that compiles
and pushes nighty QGIS builds to Dropbox. All code/server setup that is
used on the server is in the github repository. On top of that, we build
LTR (ltr-3.4 tag) and PR(final-3.4.1) tag occasionally (more precisely when
https://github.com/lutraconsulting/qgis-mac-packager is changed or tag is
moved).

Please see https://lutraconsulting.github.io/qgis-mac-packager/ and if you
have time to test and get back to me with issues or feedback.

Once the package is properly tested and I am confident it works solidly,
the next steps are probably open QEP and discuss how to do packaging as a
community. If anyone is interested in meeting or discussion please let me
know.

Cheers,
Peter


On Mon, Nov 5, 2018 at 3:43 PM Rashad Kanavath 
wrote:

>
>
> On Fri, Oct 26, 2018 at 5:26 PM Peter Petrik <
> peter.pet...@lutraconsulting.co.uk> wrote:
>
>> Hello,
>>
>> we have been asked to create standalone QGIS package for MacOS. By
>> standalone I mean that there will be a single package (.pkg) file that will
>> be extracted to /Application folder and will contain all dependencies
>> (GDAL, Python3, PyQT, Qt libraries, ...) and will be working without any
>> additional installation steps (similar to any application you install via
>> App Store).
>>
>
> Hello Peter,
>
> Did you looked into otb packaging scripts[1]. We are providing standalone
> binaries linux, windows and osx using them. It is true that python is not
> packaged but I don't see this any blocking issue to include python. Incase
> of OTB inclusion of python wasn't a requirement or priority for me. You can
> rely on osgeo4mac or whatever rather than otb's superbuild setup. Packaging
> scripts are mostly cmake and a small percentage of shell scripts.
>
> HTH
>
> [1]
> https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/tree/develop/Packaging
>
>>
>> As there is no such open-sourced solution I could use or enhance, I
>> started some prototyping here:
>> https://github.com/lutraconsulting/qgis-mac-packager . I hope I can wrap
>> the last bits next week and be able to produce QGIS 3.4 release and QGIS
>> master nightlies on some Mac Cloud server. I used osgeo4mac homebrew for
>> dependencies, since it looks like it is the most maintained package manager
>> with osgeo libraries for MacOS. Usage of Conda packages could be better,
>> but the number of downloads and the activity in any available repositories
>> is not convincing.
>>
>> The aim is to eventually have QGIS bundled and shipped similar to Linux
>> and Windows. Once we finish the work, we will send an email to the PSC and
>> see if this is something they'd be happy to bring it under their umbrella.
>>
>> I am open to any suggestions or cooperation for either packaging or
>> distribution. Feel free to
>> write me PM or reply here. Thanks
>>
>> Now its time to celebrate new QGIS release during weekend!
>>
>> Cheers,
>> Peter
>>
>> Note: CMAKE scripts try to achieve similar tasks (qgis/mac/cmake/*.in).
>> But it seems to me that only bundling of Qt libraries is actively
>> maintained [QGIS_MACAPP_BUNDLE=1]and bundling of rest of libs (gdal,
>> libzip, geos, etc.. ) [QGIS_MACAPP_BUNDLE=2 and 3] is not
>> implemented/maintained. Also I am not convinced that CMake scripting
>> language is best tool for such task. (due to reconfiguration on change,
>> syntax/readability compared to python, tools available for path handling,
>> ...)
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> --
> Regards,
>Rashad
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Rashad Kanavath]

On Fri, Oct 26, 2018 at 5:26 PM Peter Petrik <
peter.pet...@lutraconsulting.co.uk> wrote:

> Hello,
>
> we have been asked to create standalone QGIS package for MacOS. By
> standalone I mean that there will be a single package (.pkg) file that will
> be extracted to /Application folder and will contain all dependencies
> (GDAL, Python3, PyQT, Qt libraries, ...) and will be working without any
> additional installation steps (similar to any application you install via
> App Store).
>

Hello Peter,

Did you looked into otb packaging scripts[1]. We are providing standalone
binaries linux, windows and osx using them. It is true that python is not
packaged but I don't see this any blocking issue to include python. Incase
of OTB inclusion of python wasn't a requirement or priority for me. You can
rely on osgeo4mac or whatever rather than otb's superbuild setup. Packaging
scripts are mostly cmake and a small percentage of shell scripts.

HTH

[1] https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/tree/develop/Packaging


>
> As there is no such open-sourced solution I could use or enhance, I
> started some prototyping here:
> https://github.com/lutraconsulting/qgis-mac-packager . I hope I can wrap
> the last bits next week and be able to produce QGIS 3.4 release and QGIS
> master nightlies on some Mac Cloud server. I used osgeo4mac homebrew for
> dependencies, since it looks like it is the most maintained package manager
> with osgeo libraries for MacOS. Usage of Conda packages could be better,
> but the number of downloads and the activity in any available repositories
> is not convincing.
>
> The aim is to eventually have QGIS bundled and shipped similar to Linux
> and Windows. Once we finish the work, we will send an email to the PSC and
> see if this is something they'd be happy to bring it under their umbrella.
>
> I am open to any suggestions or cooperation for either packaging or
> distribution. Feel free to
> write me PM or reply here. Thanks
>
> Now its time to celebrate new QGIS release during weekend!
>
> Cheers,
> Peter
>
> Note: CMAKE scripts try to achieve similar tasks (qgis/mac/cmake/*.in).
> But it seems to me that only bundling of Qt libraries is actively
> maintained [QGIS_MACAPP_BUNDLE=1]and bundling of rest of libs (gdal,
> libzip, geos, etc.. ) [QGIS_MACAPP_BUNDLE=2 and 3] is not
> implemented/maintained. Also I am not convinced that CMake scripting
> language is best tool for such task. (due to reconfiguration on change,
> syntax/readability compared to python, tools available for path handling,
> ...)
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Regards,
   Rashad
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Peter Petrik]

Hi,

thank you Tim for your testing, it is very much appreciated.

So I tested your installer and it works nicely! My main comments and
> questions are:
>
> 1) Extended support for GDAL plugins - William’s installer goes to lengths
> to install lots of nice gal plugins etc. Will you be following suite?
>
On my list to add as many plugins as possible. Best to add ticket in the
repository if you miss some particular plugins.

2) Code signing. The experience is somewhat reduced if the user has to
> create a security exception. There have been long discussions about this
> (see e.g.
> https://lists.osgeo.org/pipermail/qgis-psc/2015-October/003315.html).
> IIRC OSGEO has the cert that we could be signing with, it would be nice to
> have everything signed and instantly usable.
>
Definitely on plan, we have bought Apple certificate for Lutra and ordered
mac on cloud server, so next installer will be signed with our key for
beginning.


> 3) DMG versos PKG - did you bundle in a pkg just for the license / readme
> step? Otherwise not just share it in a dmg?
>
It is dmg. I used https://github.com/andreyvit/create-dmg.

4) The package is nice and small - I was quite pleasantly surprised because
> I think Larry had told me their experiments with creating an application
> bundle resulted in a ~1gb .dmg
>
I think that it is very likely that you may end up with multiple instances
of the same library on various places (e.g. QT). I tried to remove
duplicates and create symlinks.


> 5) Giving the app a versioned name e.g. QGIS3.4.0 would be nicer so we can
> drop different versions into our /Applications folder and switch between
> them as needed
>
Good idea.


> 6) The readme popup on installation doesn’t look too good in dark mode
>
Created ticket for it.


> I didn’t test lots of things like using the App bundle for python
> dependencies in my IDE/standalone python stuff, GRASS support etc. etc. but
> I will say that having an all in one application bundle is something I have
> long wished for, and if we could have a code signed app bundle it would
> make the general experience of drag and drop installation so nice and
> intuitive. That said I also love the application package approach from
> William with shared frameworks and all the little details he takes care of
> to make things ‘just work’ on MacOS - it would be great if you and William
> could work together to take things forward.
>
It would be great and I am very open to closer cooperation.


> On the technical side when you build the pkg did you end up doing it all
> as a make package step with CMAKE that grabs all the deps out of brew and
> drops them into the bundle then runs otool on them to fix the library paths
> or did you manage the process externally from CMAKE using e.g. a bash
> script?
>

I used homebrew for dependancies and build QGIS with it. To add Qt,
libraries, frameworks and python stuff, I used python script that can be
found here: https://github.com/lutraconsulting/qgis-mac-packager
This eventually could be ported back to CMAKE scripts if we decide to go
that way.

Regards,
Peter



>
>
Regards
>
> Tim
>
> On 31 Oct 2018, at 12:03, Peter Petrik 
> wrote:
>
> Hi,
>
> as my prototyping goes forward, I managed to create first dmg file for 3.5
> master. If you want to try it out, here is the link:
> https://www.dropbox.com/s/vkl9oe691lkdrqh/qgis_31102018_1.dmg?dl=0
> I used Mojave 10.14, homebrew for dependecies, XCode Version 10.1 (10B61).
>
> I would be glad for any feedback, either positive or negative on PM/email
> or feel free to report the issues directly on
> https://github.com/lutraconsulting/qgis-mac-packager/issues
>
> Thanks,
> Peter
>
>
> On Tue, Oct 30, 2018 at 12:09 PM Tom Chadwin 
> wrote:
>
>> The NextGIS installer was cited to me by an expert user as the best
>> installation method of which he was aware (discussion here:
>> https://twitter.com/richardf/status/969522358640881664). I don't know how
>> useful that information is.
>>
>> Thanks
>>
>> Tom
>>
>>
>>
>> -
>> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
>> --
>> Sent from:
>> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
>
>
>
>
> ---
>
> *Tim Sutton*
> t...@qgis.org
>
>
>
>
>
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Paolo Cavallini]

Hi all,


Il 11/02/2018 04:40 AM, Tim Sutton ha scritto:
>
> That said I also love the application package approach from William
> with shared frameworks and all the little details he takes care of to
> make things ‘just work’ on MacOS - it would be great if you and
> William could work together to take things forward.
>
>
let me second this - I have been watching this relative lack of
cooperation around MacOS packages, and I believe it's a pity. If
QGIS.ORG can do something to make cooperation easier, please let us know.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Tim Sutton]

Hi Peter


So I tested your installer and it works nicely! My main comments and questions 
are:

1) Extended support for GDAL plugins - William’s installer goes to lengths to 
install lots of nice gal plugins etc. Will you be following suite?
2) Code signing. The experience is somewhat reduced if the user has to create a 
security exception. There have been long discussions about this (see e.g. 
https://lists.osgeo.org/pipermail/qgis-psc/2015-October/003315.html). IIRC 
OSGEO has the cert that we could be signing with, it would be nice to have 
everything signed and instantly usable.
3) DMG versos PKG - did you bundle in a pkg just for the license / readme step? 
Otherwise not just share it in a dmg?
4) The package is nice and small - I was quite pleasantly surprised because I 
think Larry had told me their experiments with creating an application bundle 
resulted in a ~1gb .dmg
5) Giving the app a versioned name e.g. QGIS3.4.0 would be nicer so we can drop 
different versions into our /Applications folder and switch between them as 
needed
6) The readme popup on installation doesn’t look too good in dark mode

I didn’t test lots of things like using the App bundle for python dependencies 
in my IDE/standalone python stuff, GRASS support etc. etc. but I will say that 
having an all in one application bundle is something I have long wished for, 
and if we could have a code signed app bundle it would make the general 
experience of drag and drop installation so nice and intuitive. That said I 
also love the application package approach from William with shared frameworks 
and all the little details he takes care of to make things ‘just work’ on MacOS 
- it would be great if you and William could work together to take things 
forward.

On the technical side when you build the pkg did you end up doing it all as a 
make package step with CMAKE that grabs all the deps out of brew and drops them 
into the bundle then runs otool on them to fix the library paths or did you 
manage the process externally from CMAKE using e.g. a bash script?

Regards

Tim

> On 31 Oct 2018, at 12:03, Peter Petrik  
> wrote:
> 
> Hi,
> 
> as my prototyping goes forward, I managed to create first dmg file for 3.5 
> master. If you want to try it out, here is the link:
> https://www.dropbox.com/s/vkl9oe691lkdrqh/qgis_31102018_1.dmg?dl=0 
> 
> I used Mojave 10.14, homebrew for dependecies, XCode Version 10.1 (10B61).
> 
> I would be glad for any feedback, either positive or negative on PM/email or 
> feel free to report the issues directly on 
> https://github.com/lutraconsulting/qgis-mac-packager/issues 
>   
> 
> Thanks,
> Peter
> 
> 
> On Tue, Oct 30, 2018 at 12:09 PM Tom Chadwin  > wrote:
> The NextGIS installer was cited to me by an expert user as the best
> installation method of which he was aware (discussion here:
> https://twitter.com/richardf/status/969522358640881664 
> ). I don't know how
> useful that information is.
> 
> Thanks
> 
> Tom
> 
> 
> 
> -
> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html 
> 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org 
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
> 
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

 




---

Tim Sutton
t...@qgis.org






smime.p7s
Description: S/MIME cryptographic signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Peter Petrik]

Hi,

as my prototyping goes forward, I managed to create first dmg file for 3.5
master. If you want to try it out, here is the link:
https://www.dropbox.com/s/vkl9oe691lkdrqh/qgis_31102018_1.dmg?dl=0
I used Mojave 10.14, homebrew for dependecies, XCode Version 10.1 (10B61).

I would be glad for any feedback, either positive or negative on PM/email
or feel free to report the issues directly on
https://github.com/lutraconsulting/qgis-mac-packager/issues

Thanks,
Peter


On Tue, Oct 30, 2018 at 12:09 PM Tom Chadwin 
wrote:

> The NextGIS installer was cited to me by an expert user as the best
> installation method of which he was aware (discussion here:
> https://twitter.com/richardf/status/969522358640881664). I don't know how
> useful that information is.
>
> Thanks
>
> Tom
>
>
>
> -
> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Tom Chadwin]

The NextGIS installer was cited to me by an expert user as the best
installation method of which he was aware (discussion here:
https://twitter.com/richardf/status/969522358640881664). I don't know how
useful that information is.

Thanks

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Peter Petrik]

Hi,

I agree that QEP would be very good thing to do. The python prototype and
this mailing thread are my first steps to fully understand the extent of
the task. Thank you all for the suggestions.

Peter

On Sat, Oct 27, 2018 at 7:07 PM William Kyngesburye 
wrote:

> More notes -
>
> There may be some terminology confusion here - packaging as I see it is
> making a distributable installation, either an installer or a simple
> drag-n-drop, on a disk image or zipped.
>
> The install step of the build process is where the bundling happens.
> Since this is part of the make install step, bundling needs to be done with
> cmake.  It can be customized per build with a user cmake script with the
> QGIS_MACAPP_BUNDLE_USER option, that's what I do for bundling GRASS and
> SAGA and a couple other extra libs.  If cmake is not enough, the user cmake
> can run some other script (sh or python or whatever) and pass on needed
> cmake variables to it.
>
> Adding more bundling options would have to be flexible enough to not be
> stuck on a specific distribution of external stuff (ie I prefer the
> standard Python distribution, others may want Anaconda or something else).
> Note that Python bundling would also have to cover extra modules needed by
> built-in plugins.
>
> Packaging is not covered in the build process.  It's really a personal
> preference thing, but I suppose there could be an official script.  My main
> suggestion here is that it should be a standard Apple installer package,
> not a 3rd party installer system, and especially not as an executable.
> Non-Apple installers may use a proprietary or obscured storage/compression
> system, and I know what the Apple installer executable is doing.  There are
> tools to extract files from packages if I want to look at the guts before
> installing.
>
> Side rant - it's unfortunate that Apple is pushing people into the app
> store mindset.  That's not a good comparison for QGIS, since the QGIS
> license doesn't work for the Apple app store, and there are many external
> compenents of QGIS that are usable on their own and in different
> combinations that would be harder (and more confusing) if combined into a
> single app.  Also, comparing different systems is not fair either, Linux
> and Windows and macOS are very different.  Just because others do it
> shouldn't be the main reason to do something (does Linux have an "all in
> one" installer, or does it just seem like it because of the packaging
> system?).
>
> Also note, a single "pkg" installer can still install components outside
> the main app, though App Store apps are restricted from this, I think.
>
> One option could be to still have separate external components (GDAL,
> Python, maybe GRASS), but merge them into one mega-installer.  I think it
> may be possible with the Apple installer packages but it may need a
> 3rd-party solution or a script (Applescript or Automator might work, so
> it's a double-clickable app).
>
> One more note: building for older macOS versions is a bit tricky. I'm
> doing some hackery to use an older SDK than is available in the Xcode on my
> system (on my 10.12, Xcode only has the 10.12 SDK, but I'm building for
> 10.10 using an old Xcode 10.10 SDK).  Building with a stock Xcode has only
> the latest SDK, so building for an earlier system might be a problem.
>
> It used to be a problem, with different system versions having some
> different symbol names, but this was because Apple was updating their POSIX
> support, and I think that's all done.  I've heard that you can build for an
> earlier target than the SDK version now, but I haven't tried it.  And it
> still might be tricky if a library forces a SDK version (ie Qt 5.11 adds in
> a 10.11 SDK deployment target)
>
> So, after all that, my suggestions:
>
> - expand the current cmake bundling options to more external libraries,
> but leave the big items like Python (complex, many choices) and GRASS
> (complex, normally it's own app) to packager's user bundle scripts
>
> - work on an actual "packaging" script - purpose is to package QGIS app
> (with whatever is bundled in the app) into an Apple installer package, this
> would be an all-in-one if user bundling includes EVERYTHING
>
> - consider a mega-packaging script/app to handle separate external
> companion installers, in the case where separate external component
> installations are desired
>
> On Oct 26, 2018, at 6:53 PM, William Kyngesburye 
> wrote:
>
> I created the Mac app bundle option.  I never fully extended it to 3rd
> party libraries because I don't have much interest in hiding the GDAL
> stuff.  Rather than do something new, I think this should be expanded.
>
> Also, there is the problem of extra GDAL formats.  I include everything
> non-GPL or commercial that I can in my GDAL Complete, with extra plugins
> for the GPL and commercial stuff - ECW, MrSID, GRASS (not completely sure
> about that one, GPL-wise), FileGDB, GeoPDF (Poppler).
>
> In a full bundled QGIS, I don't think 

Re: [QGIS-Developer] MacOS packaging

[William Kyngesburye]

I created the Mac app bundle option.  I never fully extended it to 3rd party 
libraries because I don't have much interest in hiding the GDAL stuff.  Rather 
than do something new, I think this should be expanded.

Also, there is the problem of extra GDAL formats.  I include everything non-GPL 
or commercial that I can in my GDAL Complete, with extra plugins for the GPL 
and commercial stuff - ECW, MrSID, GRASS (not completely sure about that one, 
GPL-wise), FileGDB, GeoPDF (Poppler).

In a full bundled QGIS, I don't think bundling ECW or MrSID would work.  So 
you'd still need a plugin installer (not a QGIS plugin) to add those to QGIS in 
some sort of global application support location like I do with GDAL now.

> On Oct 26, 2018, at 10:56 AM, Denis Rouzaud  wrote:
> 
> Hi Peter,
> 
> This is great news!
> 
> Le ven. 26 oct. 2018 à 11:26, Peter Petrik 
>  > a écrit :
> Hello,
> 
> we have been asked to create standalone QGIS package for MacOS. By standalone 
> I mean that there will be a single package (.pkg) file that will be extracted 
> to /Application folder and will contain all dependencies (GDAL, Python3, 
> PyQT, Qt libraries, ...) and will be working without any additional 
> installation steps (similar to any application you install via App Store). 
> 
> As there is no such open-sourced solution I could use or enhance, I started 
> some prototyping here: https://github.com/lutraconsulting/qgis-mac-packager 
>  . I hope I can wrap 
> the last bits next week and be able to produce QGIS 3.4 release and QGIS 
> master nightlies on some Mac Cloud server. I used osgeo4mac homebrew for 
> dependencies, since it looks like it is the most maintained package manager 
> with osgeo libraries for MacOS. Usage of Conda packages could be better, but 
> the number of downloads and the activity in any available repositories is not 
> convincing.
> 
> Is Qt Mac Deploy of any help here?
> http://doc.qt.io/qt-5/osx-deployment.html#macdeploy 
> 
>  
> 
> The aim is to eventually have QGIS bundled and shipped similar to Linux and 
> Windows. Once we finish the work, we will send an email to the PSC and see if 
> this is something they'd be happy to bring it under their umbrella.
> 
> I am open to any suggestions or cooperation for either packaging or 
> distribution. Feel free to 
> write me PM or reply here. Thanks
> 
> I'd be happy to take part of the effort. 
> 
> Now its time to celebrate new QGIS release during weekend! 
> 
> Cheers,
> Peter
> 
> Note: CMAKE scripts try to achieve similar tasks (qgis/mac/cmake/*.in). But 
> it seems to me that only bundling of Qt libraries is actively maintained 
> [QGIS_MACAPP_BUNDLE=1]and bundling of rest of libs (gdal, libzip, geos, etc.. 
> ) [QGIS_MACAPP_BUNDLE=2 and 3] is not implemented/maintained. Also I am not 
> convinced that CMake scripting language is best tool for such task. (due to 
> reconfiguration on change, syntax/readability compared to python, tools 
> available for path handling, ...)
> 
> CMake syntax is not really nice to read (maybe it's personal), but the point 
> is that all the logic is already written and accessible there, mainly in 
> terms of dependancy and library location.
> I think it makes sense to try to keep the logic in a single place if 
> reasonably possible.
> 
> The QGIS_MACAPP_BUNDLE is indeed an non completed work from Larry. But as 
> pointed out, he's also working on something lately.
> 
> More generally speaking, and even though nothing is written in QGIS source 
> code yet, I think that this project is a very good candidate for a QEP. 
> Do you have any intention to do one?
> Is the decision to go for Python and not CMake definitive for your project or 
> was it more a first quick try?
> 
> I hope my message did not sound too pessimistic. Moving towards a solution to 
> get a complete package for QGIS that is openly maintained in the community is 
> really great and I'm really glad you started this!
> 
> Cheers,
> Denis
> 
> -- 
> Denis Rouzaud
> de...@opengis.ch  
> +41 76 370 21 22 <>
> 
>  <>___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

-
William Kyngesburye 
http://www.kyngchaos.com/

"Time is an illusion - lunchtime doubly so."

- Ford Prefect


___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Denis Rouzaud]

Hi Peter,

This is great news!

Le ven. 26 oct. 2018 à 11:26, Peter Petrik <
peter.pet...@lutraconsulting.co.uk> a écrit :

> Hello,
>
> we have been asked to create standalone QGIS package for MacOS. By
> standalone I mean that there will be a single package (.pkg) file that will
> be extracted to /Application folder and will contain all dependencies
> (GDAL, Python3, PyQT, Qt libraries, ...) and will be working without any
> additional installation steps (similar to any application you install via
> App Store).
>
> As there is no such open-sourced solution I could use or enhance, I
> started some prototyping here:
> https://github.com/lutraconsulting/qgis-mac-packager . I hope I can wrap
> the last bits next week and be able to produce QGIS 3.4 release and QGIS
> master nightlies on some Mac Cloud server. I used osgeo4mac homebrew for
> dependencies, since it looks like it is the most maintained package manager
> with osgeo libraries for MacOS. Usage of Conda packages could be better,
> but the number of downloads and the activity in any available repositories
> is not convincing.
>

Is Qt Mac Deploy of any help here?
http://doc.qt.io/qt-5/osx-deployment.html#macdeploy


>
> The aim is to eventually have QGIS bundled and shipped similar to Linux
> and Windows. Once we finish the work, we will send an email to the PSC and
> see if this is something they'd be happy to bring it under their umbrella.
>
> I am open to any suggestions or cooperation for either packaging or
> distribution. Feel free to
> write me PM or reply here. Thanks
>

I'd be happy to take part of the effort.

>
> Now its time to celebrate new QGIS release during weekend!
>
> Cheers,
> Peter
>
> Note: CMAKE scripts try to achieve similar tasks (qgis/mac/cmake/*.in).
> But it seems to me that only bundling of Qt libraries is actively
> maintained [QGIS_MACAPP_BUNDLE=1]and bundling of rest of libs (gdal,
> libzip, geos, etc.. ) [QGIS_MACAPP_BUNDLE=2 and 3] is not
> implemented/maintained. Also I am not convinced that CMake scripting
> language is best tool for such task. (due to reconfiguration on change,
> syntax/readability compared to python, tools available for path handling,
> ...)
>

CMake syntax is not really nice to read (maybe it's personal), but the
point is that all the logic is already written and accessible there, mainly
in terms of dependancy and library location.
I think it makes sense to try to keep the logic in a single place if
reasonably possible.

The QGIS_MACAPP_BUNDLE is indeed an non completed work from Larry. But as
pointed out, he's also working on something lately.

More generally speaking, and even though nothing is written in QGIS source
code yet, I think that this project is a very good candidate for a QEP.
Do you have any intention to do one?
Is the decision to go for Python and not CMake definitive for your project
or was it more a first quick try?

I hope my message did not sound too pessimistic. Moving towards a solution
to get a complete package for QGIS that is openly maintained in the
community is really great and I'm really glad you started this!

Cheers,
Denis

-- 

Denis Rouzaud
de...@opengis.ch  
+41 76 370 21 22
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Saber Razmjooei]

Hi Alessandro,

One of the reasons we'd like to get MacOS packaging sorted is to ensure it
is not reliant on a single individual. We have tried and made efforts to
liaise with the rest of devs who have been active on MacOS packaging. But
we'd like to have things in place for 3.4 LTR. Others might have different
priorities.

Regards
Saber

On Fri, 26 Oct 2018 at 16:36, Alessandro Pasotti  wrote:

> Hi Peter,
>
> this is great news for Mac users!
>
> I suggest you to get in touch with Larry Shaffer, if I'm not wrong he has
> been doing some work on QGIS for conda recently, perhaps you could join
> efforts.
>
>
>
> On Fri, Oct 26, 2018 at 5:26 PM Peter Petrik <
> peter.pet...@lutraconsulting.co.uk> wrote:
>
>> Hello,
>>
>> we have been asked to create standalone QGIS package for MacOS. By
>> standalone I mean that there will be a single package (.pkg) file that will
>> be extracted to /Application folder and will contain all dependencies
>> (GDAL, Python3, PyQT, Qt libraries, ...) and will be working without any
>> additional installation steps (similar to any application you install via
>> App Store).
>>
>> As there is no such open-sourced solution I could use or enhance, I
>> started some prototyping here:
>> https://github.com/lutraconsulting/qgis-mac-packager . I hope I can wrap
>> the last bits next week and be able to produce QGIS 3.4 release and QGIS
>> master nightlies on some Mac Cloud server. I used osgeo4mac homebrew for
>> dependencies, since it looks like it is the most maintained package manager
>> with osgeo libraries for MacOS. Usage of Conda packages could be better,
>> but the number of downloads and the activity in any available repositories
>> is not convincing.
>>
>> The aim is to eventually have QGIS bundled and shipped similar to Linux
>> and Windows. Once we finish the work, we will send an email to the PSC and
>> see if this is something they'd be happy to bring it under their umbrella.
>>
>> I am open to any suggestions or cooperation for either packaging or
>> distribution. Feel free to
>> write me PM or reply here. Thanks
>>
>> Now its time to celebrate new QGIS release during weekend!
>>
>> Cheers,
>> Peter
>>
>> Note: CMAKE scripts try to achieve similar tasks (qgis/mac/cmake/*.in).
>> But it seems to me that only bundling of Qt libraries is actively
>> maintained [QGIS_MACAPP_BUNDLE=1]and bundling of rest of libs (gdal,
>> libzip, geos, etc.. ) [QGIS_MACAPP_BUNDLE=2 and 3] is not
>> implemented/maintained. Also I am not convinced that CMake scripting
>> language is best tool for such task. (due to reconfiguration on change,
>> syntax/readability compared to python, tools available for path handling,
>> ...)
>>
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> --
> Alessandro Pasotti
> w3:   www.itopen.it
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Saber Razmjooei
www.lutraconsulting.co.uk
+44 (0)7568 129733
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] MacOS packaging

[Alessandro Pasotti]

Hi Peter,

this is great news for Mac users!

I suggest you to get in touch with Larry Shaffer, if I'm not wrong he has
been doing some work on QGIS for conda recently, perhaps you could join
efforts.



On Fri, Oct 26, 2018 at 5:26 PM Peter Petrik <
peter.pet...@lutraconsulting.co.uk> wrote:

> Hello,
>
> we have been asked to create standalone QGIS package for MacOS. By
> standalone I mean that there will be a single package (.pkg) file that will
> be extracted to /Application folder and will contain all dependencies
> (GDAL, Python3, PyQT, Qt libraries, ...) and will be working without any
> additional installation steps (similar to any application you install via
> App Store).
>
> As there is no such open-sourced solution I could use or enhance, I
> started some prototyping here:
> https://github.com/lutraconsulting/qgis-mac-packager . I hope I can wrap
> the last bits next week and be able to produce QGIS 3.4 release and QGIS
> master nightlies on some Mac Cloud server. I used osgeo4mac homebrew for
> dependencies, since it looks like it is the most maintained package manager
> with osgeo libraries for MacOS. Usage of Conda packages could be better,
> but the number of downloads and the activity in any available repositories
> is not convincing.
>
> The aim is to eventually have QGIS bundled and shipped similar to Linux
> and Windows. Once we finish the work, we will send an email to the PSC and
> see if this is something they'd be happy to bring it under their umbrella.
>
> I am open to any suggestions or cooperation for either packaging or
> distribution. Feel free to
> write me PM or reply here. Thanks
>
> Now its time to celebrate new QGIS release during weekend!
>
> Cheers,
> Peter
>
> Note: CMAKE scripts try to achieve similar tasks (qgis/mac/cmake/*.in).
> But it seems to me that only bundling of Qt libraries is actively
> maintained [QGIS_MACAPP_BUNDLE=1]and bundling of rest of libs (gdal,
> libzip, geos, etc.. ) [QGIS_MACAPP_BUNDLE=2 and 3] is not
> implemented/maintained. Also I am not convinced that CMake scripting
> language is best tool for such task. (due to reconfiguration on change,
> syntax/readability compared to python, tools available for path handling,
> ...)
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Alessandro Pasotti
w3:   www.itopen.it
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] MacOS packaging

[Peter Petrik]

Hello,

we have been asked to create standalone QGIS package for MacOS. By
standalone I mean that there will be a single package (.pkg) file that will
be extracted to /Application folder and will contain all dependencies
(GDAL, Python3, PyQT, Qt libraries, ...) and will be working without any
additional installation steps (similar to any application you install via
App Store).

As there is no such open-sourced solution I could use or enhance, I started
some prototyping here: https://github.com/lutraconsulting/qgis-mac-packager
. I hope I can wrap the last bits next week and be able to produce QGIS 3.4
release and QGIS master nightlies on some Mac Cloud server. I used
osgeo4mac homebrew for dependencies, since it looks like it is the most
maintained package manager with osgeo libraries for MacOS. Usage of Conda
packages could be better, but the number of downloads and the activity in
any available repositories is not convincing.

The aim is to eventually have QGIS bundled and shipped similar to Linux and
Windows. Once we finish the work, we will send an email to the PSC and see
if this is something they'd be happy to bring it under their umbrella.

I am open to any suggestions or cooperation for either packaging or
distribution. Feel free to
write me PM or reply here. Thanks

Now its time to celebrate new QGIS release during weekend!

Cheers,
Peter

Note: CMAKE scripts try to achieve similar tasks (qgis/mac/cmake/*.in). But
it seems to me that only bundling of Qt libraries is actively maintained [
QGIS_MACAPP_BUNDLE=1]and bundling of rest of libs (gdal, libzip, geos,
etc.. ) [QGIS_MACAPP_BUNDLE=2 and 3] is not implemented/maintained. Also I
am not convinced that CMake scripting language is best tool for such task.
(due to reconfiguration on change, syntax/readability compared to python,
tools available for path handling, ...)
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer