Support for M1 Macs

[cameronmcefee]

Howdy 🤠 ,

I'm trying to run a script to build an installer that I haven't run in a handful of years, and have never run on my M1 mac. I'm getting errors that I suspect are related either to being on an M1 or 64bit. I'm curious if you can confirm if M1s are supported so I could rule that out as the source of the issue.

yarn innosetup-compiler ./config/windows-installer.iss
(node:4539) UnhandledPromiseRejectionWarning: Error: spawn Unknown system error -86
    at ChildProcess.spawn (internal/child_process.js:405:11)
    at spawn (child_process.js:677:9)
    at spawnWithSignal (child_process.js:911:17)
    at /…/node_modules/innosetup-compiler/lib/iscc.js:48:21
    at new Promise (<anonymous>)
    at Function.module.exports (/…/node_modules/innosetup-compiler/lib/iscc.js:7:19)
    at Object.<anonymous> (/…/node_modules/innosetup-compiler/lib/iscc:15:5)
    at Module._compile (internal/modules/cjs/loader.js:1085:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:4539) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:4539) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I was digging through your code and came across https://github.com/felicienfrancois/node-innosetup-compiler/blob/master/lib/iscc.js#L45 where the command wine is used instead of wine64. As an experiment, I tried changing it to wine64 which still had an error, but looked like one that indicated some progress:

yarn innosetup-compiler ./config/windows-installer.iss
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Internal error.

(node:4726) UnhandledPromiseRejectionWarning: preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000
preloader: Warning: failed to reserve range 0000000000010000-0000000000110000

(Use `node --trace-warnings ...` to show where the warning was created)
(node:4726) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:4726) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Can you please give me a sanity check and let me know if it should be working?