Konstantin Käfer

What are the use cases for running on unsupported platforms? If we can't come up with any, I think we should error for those platforms.

https://github.com/mapbox/mason/blob/master/scripts/geojson/0.3.0/script.sh 😛

https://github.com/mapbox/mason/blob/master/scripts/geojson/0.3.0/.travis.yml#L21-L30 😛

https://github.com/mapbox/mason/search?utf8=✓&q=isystem

Could be good to prove them before migrating to Circle CI ;) As a reminder, https://github.com/mapbox/jni.hpp/tree/circleci-images also exists (though I'm not sure it's the approach we should take for this...

> But for IOS it will effectively be saying that the library for both the iPhone and iPhoneSimulator is the one inside the simulator toolchain, which is wrong. I'm running...

I'm not seeing a way that would be easier, given that we need to integrate with other build systems that we don't have any control over.

I think we could support header only libaries by just using two different commands; We know when a library is header only, and it's very unlikely that they change from...

This is partially implemented in https://github.com/mapbox/mason/pull/176: If the package has a mason.ini file, it doesn't require mason to be present at all. You can add packages like this: `mason_use(variant VERSION...

Implemented in GL Native in https://github.com/mapbox/mapbox-gl-native/pull/7981