From 3edde9143ba2964f0b44d9fd057eeea0d4e5764e Mon Sep 17 00:00:00 2001 From: jpittner Date: Mon, 6 Jun 2016 13:46:34 +0200 Subject: [PATCH] Update using-native-node-modules.md Explains how native modules to be signed and packaged. --- docs/tutorial/using-native-node-modules.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/tutorial/using-native-node-modules.md b/docs/tutorial/using-native-node-modules.md index f73c1cd..82c9009 100644 --- a/docs/tutorial/using-native-node-modules.md +++ b/docs/tutorial/using-native-node-modules.md @@ -65,3 +65,8 @@ The `HOME=~/.electron-gyp` changes where to find development headers. The `--target=0.29.1` is version of Electron. The `--dist-url=...` specifies where to download the headers. The `--arch=x64` says the module is built for 64bit system. + +### Packaging and signing apps with native modules + +Native modules need to be signed. If using electron-osx-sign, be sure to include the path to the built binaries in the argument list (eg electron-osx-sign yourapp/YourApp.app yourapp/YourApp.app/Contents/Resources/app/node_modules/nativemodule/build/release/nativemodule). Also note that native modules may have intermediate files produced which should not be included (as they would also need to be signed). Add --ignore=.+\.o$ to your electron-packager build step to ignore these files (their unsigned inclusion will result in the ITMS-90135 error). + -- 2.7.4