Attempting to get 1.91 built on Mac

[Bogatyr]

Found your zip on the wayback machine. Get from here: https://drive.google.com/file/d/18qO4Gg ... sp=sharing

awesome, thanks!

[hiran]

If we found it and it is required by the mac build, should it not go to the mac deps repo?

[another_commander]

Need to ask phkb if it is really required. I don't recall him mentioning any problem with Sparkle when doing his recent test builds.

[Bogatyr]

Well, from what saw from trying to build the most recent commit, yes, both the libpng and sparkle downloads are still referenced in the build scripts in XCode, and should both be ideally hosted on oolite.space The libpng download failure is the very first failure when building the project. Sparkle missing manifests later, as Sparkle/Sparkle.h not being found, about 3/4 of the way through the build (this was of 1.90 in that case but I'd wager latest commit in master also needs this).

From my 1.90 build log:

current.url not present, assuming sparkle is out of date.
Downloading sparkle source from http://sparkle.andymatuschak.org/files/ ... 01.5b6.zip...
curl: (6) Could not resolve host: sparkle.andymatuschak.org
warning: could not download http://sparkle.andymatuschak.org/files/ ... 01.5b6.zip, using existing code originating from disk.

[Bogatyr]

Good news! 1.90 builds and runs (minimal testing, also, the test target unit tests passed) on my current build environment mentioned above (macos 10.14.6 Mojave, 2018 mac book pro, xcode 11.3.1.

All we need to get it submitted to git is a hosting place for the libpng and sparkle zips, and agreement on what branch to call it.
All I changed in the project to get it to compile and run was the download urls for libpng and sparkle, and changing C++ standard library form libstdc++ to libc++, and macOS Deployment Target from macOS 10.6 to 10.7.

If someone could create a 1.90-mac-bugfix branch or something similar, I will submit a pull request to it. These changes could also go into current master as well.

At least now there's a basis for me to continue debugging sound!

[another_commander]

Awesomesauce. mac-build-bugfix branch created. Knock yourself out, good job!

[another_commander]

I just realized mac-build-bugfix was created from master so this will be good once you have the build running on latest revision.

Until then, 1.90-mac-build-bugfix is also available and was branched out from v1.90.

[Cholmondely]

Can I presume that the now-duff oolite.org address for the Expansions Manager has been replaced with Oolite.space?

[Bogatyr]

Can I presume that the now-duff oolite.org address for the Expansions Manager has been replaced with Oolite.space?

I haven't changed that yet, but will. Whoever can add resources to oolite.space, please create:

Code: Select all

https://oolite.space/dependencies/mac/libpng-1.5.13.tar.bz2
https://oolite.org/dependencies/mac/Sparkle%201.5b6.zip

libpng-1.5.13.tar.bz2 can be sourced from http://jens.ayton.se/oolite/deps/libpng-1.5.13.tar.bz2 (at least this worked for my build)
and Sparkle from the above google drive link (a few posts back)

[another_commander]

Whoever can add resources to oolite.space, please create:

Code: Select all

https://oolite.space/dependencies/mac/libpng-1.5.13.tar.bz2
https://oolite.org/dependencies/mac/Sparkle%201.5b6.zip

libpng-1.5.13.tar.bz2 can be sourced from http://jens.ayton.se/oolite/deps/libpng-1.5.13.tar.bz2 (at least this worked for my build)
and Sparkle from the above google drive link (a few posts back)

Why oolite.space? Shouldn't those be in the github repository's Mac dependencies?

[Bogatyr]

I had assumed that minimal changes to the flow were desired. I agree it's better to put them directly into github resources.

There are these repositories:
oolite-windows-dependencies
oolite-linux-dependencies
oolite-mac-components

should there be oolite-mac-dependencies?

[Bogatyr]

Currently, in the oolite top-level repository, Cocoa-deps is not a submodule, unlike linux-deps and windows-deps, which are submodules. I could put the libpng and Sparkle unzipped components directly into the Cocoa-deps/ folder, and eliminate the download and unpacking steps from the build. Or we could use a submodule....any preferences?

[another_commander]

Directly into Cocoa-deps, for minimum confusion with submodules.

[Bogatyr]

Directly into Cocoa-deps, for minimum confusion with submodules.

Affirmative, Quite Grand Sub-Admiral!

[Cholmondely]

So how do I (a dumb pilot with no knowledge/experience about compiling anything) get a working copy of this new version of v.1.90? Is there a .dmg I can download?