-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't compile on Windows 10, VS2015 #68
Comments
Try deleting the |
Same deal here. I found that the error is Failed to load NIF library at PATH... but when checking path, I see a file there with an added extension, not mentioned in the error: http://i.imgur.com/26KY8N5.png |
Well, I see other files there, too http://imgur.com/zpXGsyZ |
Following this bit of advice seemed to fix the issue. |
Hi, I've even moved the project in a easier directory path, without underscores, blanks et (the current dir is D:\test) |
Try editing the
to:
and then run |
Hi David, Thank you very much! —Kai
|
Hey David that seemed to have solved the problem! Now it's compiling! Strange thing is that on another computer running Win7 64bit and the same other softwares on mine's (VS, Elixir/Erlang and Phoenix, same versions) didn't show the problem and instead compiled successfully. Edit: it's still giving the same error when running |
The problem seems to be when updating to a new version of Erlang or Elixir - it's then necessary to recompile the C code. |
About the errors with |
I just went through this same issue, I think it is important to mention that you cannot compile it at all unless you run the |
For 64 bit works thanks @ronnieoverby |
An update to perhaps save others a fair bit of time... Things seem to have moved on and under Windows 10 I could not find vcvarsall.bat from any way or means of installing visual studio or anything else.
Simples! |
Thanks for the update. I'll look into this further and update the docs accordingly. |
@dnarmitage if you try to create a c++ project after installing VS it will download the requisite build tools I do agree it is probably easier to download the build tools directly, since I would guess most developers using Elixir are not using Visual Studio :) Hopefully once Bash on Windows is sorted out (and Elixir works properly on it) we can avoid this whole step. |
Thanks Dylan, that makes more sense - unfortunately I didn't cotton on to
running a c++ project in VS first, so was stymied.
As you say, will be nice when we can avoid.
…On Sat, Jan 21, 2017 at 3:47 PM, Dylan Foster ***@***.***> wrote:
@dnarmitage <https://github.com/dnarmitage> if you try to create a c++
project after installing VS it will download the requisite build tools
I do agree it is probably easier to download the build tools directly,
since I would guess most developers using Elixir are not using Visual
Studio :)
Hopefully once Bash on Windows (and Elixir works properly on it) we can
avoid this whole step.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFyoJTnFIF0-p1FtsK8rOeDcwfHWXxX-ks5rUiiOgaJpZM4HH4aX>
.
|
@dementopro You need to follow the instructions that it says in your screenshot to get the Alternatively (and probably more preferred these days) is to just use WSL to run elixir. |
I've already run this command |
My steps that lead to a successful build on VS 2022 Community:
|
Îch habe, nachdem ich bcrypt_elixir Fehlermeldungen erhalten habe, ebenfalls den obigen Befehl unter VS 2019 ausgeführt und hatte keinen Erfolg. Anders als vor einem halben Jahr, als das Problem schon einmal auftauchte. Ich weiß nicht, wie ich jetzt weiter vorgehen soll. Die Ursprungsfehlermeldung bei mir lautet: |
Hi
i'm trying to compile on my main dev machine with the following setup:
When I launch
mix do deps.get, compile
from the VS2015 dev console at the root of my Elixir/Phoenix project I get the following:I've found similar error messages in previous, closed issues but I'm still unable to solve my problem with the suggestions given in these threads.
Michele
The text was updated successfully, but these errors were encountered: