fixing the binary builds

 

Hi All,

    right now at least the binary mac builds are broken because they use the latest SDK and so are unusable on anything older than 10.11.  Who holds the keys to bintray?  I'd like to try and fix this.

_,,,^..^,,,_

best, Eliot

 

On Fri, Apr 28, 2017 at 7:00 AM, Eliot Miranda <[hidden email]> wrote:

 

Hi All,

    right now at least the binary mac builds are broken because they use the latest SDK and so are unusable on anything older than 10.11.  Who holds the keys to bintray?  I'd like to try and fix this.

_,,,^..^,,,_

best, Eliot

Are we using something like [1]....  " cc   -mmacosx-version-min=10.6   -Wpartial-availability"   

and the CI might be made to fail if it sees any "introduced in macOS" warnings ?? 

http://stackoverflow.com/questions/11684302/mac-sdk-using-latest-sdk-but-ensuring-backwards-compatibility-with-earlier-depl

This could be useful...
http://www.deploymateapp.com/

A rant that is quite Insightful...

http://stackoverflow.com/questions/15091105/confusion-of-how-to-make-osx-app-backward-compatible-how-to-test-them

btw, what is the officially support OSX version?

 

On Thu, Apr 27, 2017 at 7:23 PM, Ben Coman <[hidden email]> wrote:

 

On Fri, Apr 28, 2017 at 7:00 AM, Eliot Miranda <[hidden email]> wrote:

 

Hi All,

    right now at least the binary mac builds are broken because they use the latest SDK and so are unusable on anything older than 10.11.  Who holds the keys to bintray?  I'd like to try and fix this.

_,,,^..^,,,_

best, Eliot

Are we using something like [1]....  " cc   -mmacosx-version-min=10.6   -Wpartial-availability"   

and the CI might be made to fail if it sees any "introduced in macOS" warnings ?? 

http://stackoverflow.com/questions/11684302/mac-sdk-using-latest-sdk-but-ensuring-backwards-compatibility-with-earlier-depl

I have no idea.  I don't know how the bintray builds are administered, where the repository is, who setup the bintray builds, etc.  I'm eager to talk with anyone who can enlighten me.

My understanding is that what one does is install a suitable SDK.  If you look in build.macosXXX/common/Makefile.flags you'll see the available SDKs are searched for the minimum available that works for the configuration (10.9 for 32-bit 10.10 for 64-bit).  See the build.macosXXX/HowToBuild files for info on obtaining older SDKs.

 

This could be useful...
http://www.deploymateapp.com/

A rant that is quite Insightful...

http://stackoverflow.com/questions/15091105/confusion-of-how-to-make-osx-app-backward-compatible-how-to-test-them

btw, what is the officially support OSX version?

IMO that's defined in the above files.  I've tested against the 10.9 and 10.10 SDKs.  I have a 10.9 machine and so try and keep the builds supporting 10.9.  The current binary VMs support only 10.11, and that's not good IMO.  What I want is to upgrade the bintray build to add the SDKs.  I don't know if that's possible; if the version of Xcode is compatible with that approach etc.  But since I can't get access to the bintray setup I have no idea if this is possible.

 

_,,,^..^,,,_

best, Eliot

 

On Fri, Apr 28, 2017 at 8:01 AM Tim Felgentreff <[hidden email]> wrote:

 

The Bintray builds are uploaded from travis and appveyor. Changing the yml files in the git repo we can choose the Xcode version.

You might want to have a look at [1] which lists the different Xcode environments supported by Travis.

[1] https://docs.travis-ci.com/user/osx-ci-environment/#Xcode-version

 

On Fri, Apr 28, 2017 at 4:50 PM Bert Freudenberg <[hidden email]> wrote:

On Fri, Apr 28, 2017 at 12:08 PM, Fabio Niephaus <[hidden email]> wrote:

On Fri, Apr 28, 2017 at 8:01 AM Tim Felgentreff <[hidden email]> wrote:

 

The Bintray builds are uploaded from travis and appveyor. Changing the yml files in the git repo we can choose the Xcode version.

You might want to have a look at [1] which lists the different Xcode environments supported by Travis.

[1] https://docs.travis-ci.com/user/osx-ci-environment/#Xcode-version

So it currently builds using Xcode 7.3.1 on OS X 10.11.

The only older option is Xcode 6.4 on OS X 10.10, but at least that one has the macosx10.9 SDK installed, too.

We just need to add osx_image: xcode6.4 to https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/.travis.yml

Question is, would a VM built using 6.4 still run on macOS 10.12?

I'm afraid I can't answer that question.

But if not, we could have separate builds, one with OS X 10.9-10.10 support and one for macOS 10.11-10.12.

That would require some extra work though.

 

On Fri, Apr 28, 2017 at 5:06 PM Fabio Niephaus <[hidden email]> wrote:

On Fri, Apr 28, 2017 at 4:59 PM Bert Freudenberg <[hidden email]> wrote:

On Fri, Apr 28, 2017 at 4:57 PM, Fabio Niephaus <[hidden email]> wrote:

 

On Fri, Apr 28, 2017 at 4:50 PM Bert Freudenberg <[hidden email]> wrote:

On Fri, Apr 28, 2017 at 12:08 PM, Fabio Niephaus <[hidden email]> wrote:

On Fri, Apr 28, 2017 at 8:01 AM Tim Felgentreff <[hidden email]> wrote:

 

The Bintray builds are uploaded from travis and appveyor. Changing the yml files in the git repo we can choose the Xcode version.

You might want to have a look at [1] which lists the different Xcode environments supported by Travis.

[1] https://docs.travis-ci.com/user/osx-ci-environment/#Xcode-version

So it currently builds using Xcode 7.3.1 on OS X 10.11.

The only older option is Xcode 6.4 on OS X 10.10, but at least that one has the macosx10.9 SDK installed, too.

We just need to add osx_image: xcode6.4 to https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/.travis.yml

Question is, would a VM built using 6.4 still run on macOS 10.12?

I'm afraid I can't answer that question.

But if not, we could have separate builds, one with OS X 10.9-10.10 support and one for macOS 10.11-10.12.

That would require some extra work though.

Maybe we should just try to see what happens?

Okay, let's do that then...

https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/845ae199a72cb55504cfa64c95f55ec0c00d509c

-> https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds/226849895

Seems to be working just fine on macOS Sierra:

 

 

- Bert -