Konstantin Käfer

CI build succeeds despite failure to upload

1

I've observed that [a build](https://travis-ci.org/mapbox/mason/jobs/304965873) succeeded despite the upload step failing with ``` Required library file /Users/travis/build/mapbox/mason/mason_packages/osx-x86_64/swiftshader/2017-11-20/lib/libGLESv2.dylib doesn't exist. ```

Mason wishlist

3

This ticket collects things we want to change about mason in a system redesign: - **Split building packages from using them**: There should be two parts of the system, one...

Mason CMake

4

Following https://github.com/mapbox/mason/issues/187, my long term goal is to split Mason in two pieces: A small-ish client that downloads/installs/uses packages, and a system that builds packages. We're using the CMake script...

Use -isystem to pass include paths

4

We are currently using `-I` to pass the paths to Mason packages to the compiler. However, we should be using `-isystem` to prevent warning messages from this third party code....

Boost libs: cflags + ldflags should be empty

2

The compiled boost libs are static libs, so the user should use `static_libs` to obtain the paths. However, calling `cflags` and `ldflags` on them currently either fails, or returns `-lboost_*`,...

Looks like CMake doesn't like compiling for Android without a toolchain file. We should add toolchain.cmake files to compiler packages, and populate `MASON_CMAKE_TOOLCHAIN` so that the builds pick it up...

include paths: -I vs -isystem

2

I'm seeing many custom packages that specify the same path both in `-I` and `-isystem`. Is there a particular reason to do that? In https://github.com/mapbox/mason/blob/master/mason.sh#L496, we are removing the prefix...

Improve separation between build and install

3

Currently, if a binary package is not available, Mason tries to build the package from source. However, the system may not be set up to actually compile that package. Instead,...

It's very hard to debug failures in these.

List N-API version in index.tab and on the release overview page

3

The overview page at https://nodejs.org/en/download/releases/ and the parseable index at https://nodejs.org/dist/index.tab currently list the ABI version. However, they don't yet list the N-API version. While that version hopefully won't change...