Meta ticket to state that eventually we should consider porting these scripts to Mason (https://github.com/mapbox/mason). But not now - below is my thinking:
What Mason would offer:
ability to easily build and install individual deps rather than building them all in one go+one tarball.
a command line interface to install windows packages that is the same as other platforms
However, let's keep this as an idea only right now. The current approach of a single set of scripts that create a single tarball of deps is better for fast iteration and testing of build settings that impact all deps. In other words, I think its too early still to break apart all builds like mason requires. The is a The extra work of splitting each dependency into its own branch I don't think is worth it for windows because we're still fine tuning build methods, dependency relationships, and build settings (debug flags, etc).
Additionally to make a Mason port possible we'd need to:
wilhelmberg
commented
9 years ago
Meta ticket to state that eventually we should consider porting these scripts to Mason (https://github.com/mapbox/mason). But not now - below is my thinking:
What Mason would offer:
However, let's keep this as an idea only right now. The current approach of a single set of scripts that create a single tarball of deps is better for fast iteration and testing of build settings that impact all deps. In other words, I think its too early still to break apart all builds like mason requires. The is a The extra work of splitting each dependency into its own branch I don't think is worth it for windows because we're still fine tuning build methods, dependency relationships, and build settings (debug flags, etc).
Additionally to make a Mason port possible we'd need to: