Home → Problems →

Problem while compiling with x64 platform

• Edit

edgar.osc

05 Apr, 2014 03:37 AM

Hi guys,

I'm trying to compile a node module with x64 but keep getting an issue on compile process, I had the same problem in one of my machines that was fixed by installing Visual Studio Express 2013. I was wondering what the stack for x64 libraries is?

I'm attaching a screenshot of the issue.

• appveyor_compile-error.png 152 KB

1. Support Staff 1 Posted by Feodor Fitsner on 06 Apr, 2014 05:44 PM

   

   Hi Edgar,

   I've remove Node.js x64 and installed Node.js x86 - that might fix a problem with native modules. Please give it another try and let me know how it goes.

   Source: http://stackoverflow.com/questions/17640950/error-msb007-node-js-mo...

   • Edit

2. 2 Posted by Edgar Silva on 08 Apr, 2014 02:05 AM

   

   Hi Feodor,

   We alredy solved this by doing this:
   

   # We add newest MSBuild so we can use the correct libs for the x64 version
     - cmd: SET PATH=C:\Program Files (x86)\MSBuild\12.0\bin\;%PATH%
     - cmd: SET PATH=c:\python27;%PATH%
     - cmd: set NODIST_X64=1
     - cmd: call nodist stable 2>&1
     - cmd: npm install -g node-gyp
     - cmd: ECHO "BUILDING x64 version:"
     - cmd: npm install --build-from-source --msvs_version=2013
   

   Thanks to :
   https://github.com/BergWerkGIS/node-serialport/blob/master/appveyor...

   He discovered the appropriate x64 libs were there but not being picked up sin an older version was being picked up from the registry path, or something of the sort.

   We do have a new issue though regarding the job not starting, it seems the secure environment variables are incorrect,

   Do you know if encrypted secure env vars are account bound? because we have the exact same ones in my fork and it works fine, but in my colleague's repo the job won't start.

   Thanks for your help.

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 08 Apr, 2014 02:12 AM

   

   Oh, I've just got that solution from Wilhelm the author of node-serialport and was going to share with you :) but you already found it.

   Yes, secure variables are bound to account (not user), so if you are both under the same appveyor account it should work. What error are you getting?

   - Feodor

   • Edit

4. 4 Posted by Edgar Silva on 08 Apr, 2014 02:18 AM

   

   We are not under same account or repo, just this:

   https://ci.appveyor.com/project/ChrisWilliams/node-serialport/build...

   But something similar happened to me when I had a typo in one of the secure env variables. SO I guess same thing is happening, can't decrypt since those secures are bound to my account and the job fails.

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 08 Apr, 2014 02:22 AM

   

   I see. Yeah, this is not good. I think desired behavior would be to yield empty strings, not fail. I'll fix that and deploy with tomorrow's update.

   Thanks for the catch!

   - Feodor

   • Edit

6. 6 Posted by Edgar Silva on 08 Apr, 2014 02:28 AM

   

   Anytime Feodor, thanks for the help and quick support (y)

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 10 Apr, 2014 04:51 AM

   

   Edgar,

   The bug has been fixed and update deployed.

   • Edit

8. 8 Posted by Edgar Silva on 11 Apr, 2014 06:32 PM

   

   Thanks Feodor,

   I will check when I fix a couple of warnings that are showing off in the log.

   • Edit

9. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:38 AM.