Closed quienn closed 2 years ago
note: I was just trying to install the Joy framework. This happens with all projects that are C modules.
May be the following text is relevant?
If you want to use jpm to install native extensions, you will also need to install Visual Studio, ideally a recent release (2019 or 2017 should work well). Then, running jpm from the x64 Native Tools Command Prompt should work for a 64-bit build, and from the Developer Command Prompt should work for 32-bit builds. Using these specific command prompts for jpm simply lets jpm use the Microsoft compiler to compile native modules on install.
Specifically, the bit about:
running jpm from the x64 Native Tools Command Prompt should work for a 64-bit build, and from the Developer Command Prompt should work for 32-bit builds
I tried it with all of them, and it still shows the same error...
This does look strange, probably an issue with linking to the 32 bit build. The easiest fix would be to only use the 64 bit build, since there is very little hardware out there that needs 32 bit.
also you need to clean the build if you used the wrong architecture, that would result in the same issues. Closing as cannot reproduce.
Aside from the error that's inside this issue's title, there's some other artifacts the build output shows (it's in Spanish, I'm sorry):