%1 is not a valid Win32 application #1103

govenlive · 2017-02-20T09:25:23Z

When in doubt it never hurts to ask!

Finally if you're opening an issue fill out the form below!

Thanks!
-->

SerialPort Version 4.0.7:
NodeJS Version 7.5.0 but I'm electron1.6.0:
Operating System WIN10 x64

Summary of Problem

the error

reconbot · 2017-02-20T13:56:30Z

What are you doing to get the error?

…

On Mon, Feb 20, 2017, 4:25 AM govenlive ***@***.***> wrote: When in doubt it never hurts to ask! Finally if you're opening an issue fill out the form below! Thanks! --> - *SerialPort Version* 4.0.7: - *NodeJS Version* 7.5.0 but I'm electron1.6.0: - *Operating System* WIN10 x64 Summary of Problem [image: image] <https://cloud.githubusercontent.com/assets/5742746/23118877/d17fe986-f790-11e6-8ae8-5a5fc2c84690.png> the error [image: image] <https://cloud.githubusercontent.com/assets/5742746/23118866/c0724030-f790-11e6-9294-77af276bfd99.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1103>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABlbqiRW2ruWwhuwu6gPEYePz6A96iMks5reVwDgaJpZM4MF77t> .

govenlive · 2017-02-21T03:17:01Z

I need to compile for Windows 7 32 bit run, I by electron - packager. / app MF - Control - platform = win32 -- arch = ia32 - out. / outApp - version = 1.4.13 - overwrite - icon. = / build/icon. Ico such commands to compile a 32-bit application will prompt error, but I use the build - win - x64 cheap can run normally, so I try to build - win - ia32, submitted to the following error:

H:\_projects\MF\MF-Control-Node>build --win --ia32
Rebuilding native production dependencies for win32:ia32
Error: npm.cmd exited with code 1
Output:

> serialport@4.0.7 install H:\_projects\MF\MF-Control-Node\app\node_modules\serialport
> node-pre-gyp install --fallback-to-build

�ڴ˽���������һ������һ����Ŀ����Ҫ���ò������ɣ�����
�ӡ�/m�����ء�
  serialport.cpp
  serialport_win.cpp
  win_delay_load_hook.cc
..\src\serialport.cpp(90): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ��� [
H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
..\src\serialport.cpp(102): warning C4996: 'v8::Value::ToNumber': ������Ϊ�ѷ���
 [H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8298): note: �
μ���v8::Value::ToNumber��������
..\src\serialport.cpp(174): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ���
[H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
..\src\serialport.cpp(193): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ���
[H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
..\src\serialport.cpp(217): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ���
[H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
..\src\serialport.cpp(252): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ���
[H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
..\src\serialport.cpp(369): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ���
[H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
..\src\serialport.cpp(480): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ���
[H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
..\src\serialport.cpp(528): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ���
[H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
..\src\serialport.cpp(585): warning C4996: 'v8::Value::ToInt32': ������Ϊ�ѷ���
[H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\serialport.vcxproj]
  C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\deps\v8\include\v8.h(8334): note: �
μ���v8::Value::ToInt32��������
C:\Users\hasee\.electron-gyp\.node-gyp\iojs-1.4.13\Release\iojs.lib : fatal error LNK1106
: �ļ���Ч����������: �޷����ҵ� 0xED5E2 [H:\_projects\MF\MF-Control-N
ode\app\node_modules\serialport\build\serialport.vcxproj]
Failed to execute 'C:\Program Files\nodejs\node.exe H:\_projects\MF\MF-Control-Node\app\n
ode_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --module=H:\_projects\MF\M
F-Control-Node\app\node_modules\serialport\build\Release\serialport.node --module_name=se
rialport --module_path=H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\
Release' (1)

Error output:
gyp ERR! build error 
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with e
xit code: 1
gyp ERR! stack     at ChildProcess.onExit (H:\_projects\MF\MF-Control-Node\app\node_modul
es\node-gyp\lib\build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:192:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:
12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "H:\\_projects\\MF\\MF-Control-Nod
e\\app\\node_modules\\node-gyp\\bin\\node-gyp.js" "build" "--fallback-to-build" "--module
=H:\\_projects\\MF\\MF-Control-Node\\app\\node_modules\\serialport\\build\\Release\\seria
lport.node" "--module_name=serialport" "--module_path=H:\\_projects\\MF\\MF-Control-Node\
\app\\node_modules\\serialport\\build\\Release"
gyp ERR! cwd H:\_projects\MF\MF-Control-Node\app\node_modules\serialport
gyp ERR! node -v v7.5.0
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe H:\_pr
ojects\MF\MF-Control-Node\app\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-b
uild --module=H:\_projects\MF\MF-Control-Node\app\node_modules\serialport\build\Release\s
erialport.node --module_name=serialport --module_path=H:\_projects\MF\MF-Control-Node\app
\node_modules\serialport\build\Release' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (H:\_projects\MF\MF-Control-Node\
app\node_modules\serialport\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:192:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:890:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:226:5)
node-pre-gyp ERR! System Windows_NT 10.0.14393
node-pre-gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "H:\\_projects\\MF\\MF-Co
ntrol-Node\\app\\node_modules\\serialport\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp"
 "install" "--fallback-to-build"
node-pre-gyp ERR! cwd H:\_projects\MF\MF-Control-Node\app\node_modules\serialport
node-pre-gyp ERR! node -v v7.5.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.32
node-pre-gyp ERR! not ok 

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\hasee\\AppData\\Roaming\\
npm\\node_modules\\npm\\bin\\npm-cli.js" "rebuild" "serialport" "node-sass"
npm ERR! node v7.5.0
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! serialport@4.0.7 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the serialport@4.0.7 install script 'node-pre-gyp install --fallback-t
o-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     H:\_projects\MF\MF-Control-Node\app\npm-debug.log

    at ChildProcess.childProcess.once.code (C:\Users\hasee\AppData\Roaming\npm\node_modul
es\electron-builder\node_modules\electron-builder-util\src\util.ts:134:14)
    at Object.onceWrapper (events.js:291:19)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:192:7)
    at maybeClose (internal/child_process.js:890:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
From previous event:
    at Promise.longStackTracesCaptureStackTrace [as _captureStackTrace] (C:\Users\hasee\A
ppData\Roaming\npm\node_modules\electron-builder\node_modules\.3.4.7@bluebird\js\release\
debuggability.js:397:19)
    at Promise._then (C:\Users\hasee\AppData\Roaming\npm\node_modules\electron-builder\no
de_modules\.3.4.7@bluebird\js\release\promise.js:231:17)
    at Promise._passThrough (C:\Users\hasee\AppData\Roaming\npm\node_modules\electron-bui
lder\node_modules\.3.4.7@bluebird\js\release\finally.js:91:17)
    at Promise.lastly.Promise.finally (C:\Users\hasee\AppData\Roaming\npm\node_modules\el
ectron-builder\node_modules\.3.4.7@bluebird\js\release\finally.js:100:17)
    at new PromiseSpawn (C:\Users\hasee\AppData\Roaming\npm\node_modules\electron-builder
\node_modules\.3.4.7@bluebird\js\release\generators.js:36:34)
    at C:\Users\hasee\AppData\Roaming\npm\node_modules\electron-builder\node_modules\.3.4
.7@bluebird\js\release\generators.js:197:21
    at build (C:\Users\hasee\AppData\Roaming\npm\node_modules\electron-builder\out\builde
r.js:71:21)
    at Object.<anonymous> (C:\Users\hasee\AppData\Roaming\npm\node_modules\electron-build
er\out\cli\build-cli.js:71:41)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:418:7)
    at startup (bootstrap_node.js:139:9)
    at bootstrap_node.js:533:3

reconbot · 2017-02-21T14:45:15Z

You can download 32 bit builds from our releases page. https://github.com/EmergingTechnologyAdvisors/node-serialport/releases

reconbot · 2017-06-20T03:10:01Z

I'm going to close this issue due to it's age, but if you'd like to continue with it feel free to comment and we'll reopen.

reconbot added the support label Feb 21, 2017

akaJes mentioned this issue May 30, 2017

electron-builder cross platform rebuild #1180

Closed

reconbot closed this as completed Jun 20, 2017

lock bot locked and limited conversation to collaborators Apr 8, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

%1 is not a valid Win32 application #1103

%1 is not a valid Win32 application #1103

govenlive commented Feb 20, 2017

reconbot commented Feb 20, 2017 via email

govenlive commented Feb 21, 2017 •

edited by reconbot

Loading

reconbot commented Feb 21, 2017

reconbot commented Jun 20, 2017

%1 is not a valid Win32 application #1103

%1 is not a valid Win32 application #1103

Comments

govenlive commented Feb 20, 2017

Summary of Problem

reconbot commented Feb 20, 2017 via email

govenlive commented Feb 21, 2017 • edited by reconbot Loading

reconbot commented Feb 21, 2017

reconbot commented Jun 20, 2017

govenlive commented Feb 21, 2017 •

edited by reconbot

Loading