ext only buildable on mac 10.12 about multibuild HOT 5 OPEN

Do you mean, set the value of MACOSX_DEPLOYMENT_TARGET ? That's normally done when building against Python - the flag value comes from Python's configuration, but I believe you can set this variable in your .travis.yml file, before your builds, and it should work. Did you try already?

from multibuild.

Thanks, with that flag set to 10.12 I can successfully build a wheel: macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.
Is it possible to build a wheel for 10.12?

from multibuild.

Erm - if you really set MACOSX_DEPLOYMENT_TARGET, and it worked, then that wheel should be compatible with 10.12 and above, only. I can't remember the details of how the filename gets its flags, but if it's only >= 10.12 compatible, then you can / should rename it to reflect that, in case some innocent 10.11 user tries to install it via pip.

I guess what you want to do, is set MACOSX_DEPLOYMENT_TARGET to the minimum it will build on (maybe 10.9?) and name accordingly.

from multibuild.

Here is the log for build on travis: https://travis-ci.org/google/protobuf/jobs/337078207
You can find one line is: creating build/lib.macosx-10.6-intel-2.7
On my local mac (10.12), it's 10.12-x86-64-2.7.
Is there any macro I can use to change the behavior on travis to the same as my local mac?

from multibuild.

I believe that the wheel you have built will in fact be compatible with OSX 10.9 and above. You can test that by running the tests on a travis xcode image running 10.9.

I believe therefore, that the wheel name is not a correct indicator of compatibility. Specifically, I think the 10.6 label comes from the Python.org Python installer that gets downloaded during the multibuild build.

You can just rename the wheel in your script to have platform part macosx_10_9_intel, this should then be picked up by installing systems >= 10.9 - is that what you intend?

from multibuild.