So I found that there was a bug in my scripts and I am trying to fix that (but 
am struggling a bit with oddities in how the GitHub actions deal with files 
that are folders. I should have that fixed soon so that in the future there 
will again be Subsurface.app.zip files as part of the releases.

/D

> On Nov 18, 2019, at 10:25 AM, Martin de Weger <[email protected]> wrote:
> 
> Hi Dirk,
> 
> I didn’t see the app version, so I tried to work my way through the build. 
> I’ll check from time to time if there is a (newer) version for the Mac so I 
> can play around a bit. No worries on pushing it especially for me.
> 
> 
> Met vriendelijke groeten,
> 
> Martin de Weger
> 
> 
> 
> 
> 
>> Op 18 nov. 2019, om 17:11 heeft Dirk Hohndel <[email protected] 
>> <mailto:[email protected]>> het volgende geschreven:
>> 
>> I pointed Martin at the release link so he would be able to download 
>> binaries. I didn't expect anyone to start from those sources, frankly (they 
>> are automatically put there by GitHub, I don't think I can turn this off). 
>> Building Subsurface from non-git sources is actually harder than just from a 
>> cloned git repository!
>> 
>> Usually all the main binaries are in that directory 
>> https://github.com/Subsurface-divelog/subsurface/releases/tag/ci-release 
>> <https://github.com/Subsurface-divelog/subsurface/releases/tag/ci-release>, 
>> but sometimes one or more are missing because of issues with the way I 
>> implemented the uploading of releases. It looks like the latest set is 
>> missing the macOS .app.zip file :-(
>> 
>> I can push a current binary to the Subsurface website download area... and I 
>> can try and figure out a way to make the upload or the CICD builds more 
>> reliable - unfortunately the latest upload looks like it succeeded and 
>> somehow ended up getting overwritten / deleted by another build...
>> 
>> Unless you are planning to work on the code itself, I would strongly 
>> encourage people to just test with the builds we provide as that is much 
>> more indicative of what our users will experience as well.
>> 
>> /D
>> 
>>> On Nov 18, 2019, at 2:38 AM, Anton Lundin <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> On 17 November, 2019 - Martin de Weger wrote:
>>> 
>>>> Hi Guys,
>>>> 
>>>> I’ve downloaded the latest developer release from 
>>>> https://github.com/Subsurface-divelog/subsurface/releases/tag/ci-release 
>>>> <https://github.com/Subsurface-divelog/subsurface/releases/tag/ci-release> 
>>>> <https://github.com/Subsurface-divelog/subsurface/releases/tag/ci-release 
>>>> <https://github.com/Subsurface-divelog/subsurface/releases/tag/ci-release>>
>>>>  and unpacked it at ~/Software/subsurface. After reading the Install file 
>>>> I executed cd ~/Software/subsurface/..; bash 
>>>> ~/Software/subsurface/scripts/build.sh -build-deps -desktop from the 
>>>> terminal. As a result, I get the following output. 
>>> 
>>> 
>>> The ci-release tag is used to provide current dev builds, so if you only
>>> would like to run a dev-build of subsurface you should be able to
>>> download a Subsurface.app.zip from the ci-release page. Obviously there
>>> is a bug somewhere that causes it to not show up right now.
>>> 
>>> If you would like to build your own latest and greatest subsurface
>>> binaries, I'd suggest you clone the repo instead of downloading a
>>> ci-release snapshot of the source.
>>> 
>>> 
>>>> building Subsurface in subsurface/build
>>>> Building in /Users/martinw/Software, installing in 
>>>> /Users/martinw/Software/install-root
>>>> cannot find qmake or qmake-qt5
>>>> 
>>>> What am I missing? I have QT 5.13.2 installed in my app folder.
>>> 
>>> 
>>> You need to have qmake in your path, or point it out with
>>> QMAKE=path/to/qmake or by pointing CMAKE_PREFIX_PATH to the cmake files
>>> in your qt install.
>>> 
>>> 
>>> //Anton
>>> 
>>> 
>>> -- 
>>> Anton Lundin        +46702-161604
>>> _______________________________________________
>>> subsurface mailing list
>>> [email protected] <mailto:[email protected]>
>>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface 
>>> <http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface>
>> 
>> _______________________________________________
>> subsurface mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
> 

_______________________________________________
subsurface mailing list
[email protected]
http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface

Reply via email to