nw-builder has been producing invalid frameworks at least since
2017, at it seems there's no progress in fixing it (see
https://github.com/nwjs/nw.js/issues/6338). To workaround this problem,
we use macapptool to proper seal all the framework resources so it
can be signed and passes the validations required for notarization.
Since we're introducing this dependency, we can also use macapptool
to simplify signing and notarization.
To create a signed macOS build, pass the --codesign flag.
--codesign-identity can be used to use a non-default identity
("Developer ID")
To notarize a signed bundle, use the --notarize flag. There are
also flags provided to specify the username/password for the
notarization service.
* Offline missions (with FC disconnected) are now available for load and save to file.
Supports XML file format, should be compatible enough with other software
* removed default file name
* removed code in early stage of future developments
* code style and fc buttons
* map resize handling
* fix include nwdialog and fs packages
* xml2js lib with all dependencies in a single file
- Remove usages of runSequence(), which doesn't work with Gulp 4,
using gulp.series() instead.
- Add support for linux32 builds
- Add new --platform argument for building only for a single platform
(e.g. --platform=osx64).
Fixes build problems introduced in #527Fixes#531
When a controllable VTX is configured, a new section appears in
the configuration tab which allows the user to set the band, channel
power and "low power on disarm" option.
runSequence will return immediately, so tasks depending on
dist might fail the first time they're run. By explicitely passing
the callback, gulp will wait until runSequence runs both clean
and dist-build until it considers dist finished.