There’s a 0.22.0-rc.1 release that got out like 45 minutes ago.
@maciejgryka What you have shown have worked for me for Elixir 1.12.0-otp-24 and Erlang 24.0.1. Thanks!
(I still used rustler from the master branch, though.)
dimitarvp
4
CharlesO
Still have the same issues after this update. Previously working code will not compile anymore.
Compiling quote v1.0.7
Compiling rustler_codegen v0.22.0-rc.1
error[E0432]: unresolved imports `rustler_sys::TWinDynNifCallbacks`, `rustler_sys::WIN_DYN_NIF_CALLBACKS`
--> C:\Users\Charles Okwuagwu\.cargo\registry\src\github.com-1ecc6299db9ec823\rustler-0.22.0-rc.1\src\codegen_runtime.rs:16:23
|
16 | pub use rustler_sys::{TWinDynNifCallbacks, WIN_DYN_NIF_CALLBACKS};
| ^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^ no `WIN_DYN_NIF_CALLBACKS` in the root
| |
| no `TWinDynNifCallbacks` in the root
error: aborting due to previous error
For more information about this error, try `rustc --explain E0432`.
error: could not compile `rustler`
To learn more, run the command again with --verbose.
== Compilation error in file lib/nif.ex ==
** (RuntimeError) Rust NIF compile error (rustc exit code 101)
(rustler 0.22.0-rc.1) lib/rustler/compiler.ex:36: Rustler.Compiler.compile_crate/2
lib/nif.ex:2: (module)
(stdlib 3.15) erl_eval.erl:685: :erl_eval.do_apply/6
0
dimitarvp
CharlesO
defp deps do
[
{:tzdata, "~> 1.1.0"},
{:gen_smtp, "~> 1.0"},
{:mime, "~> 1.4"},
{:fs, "~> 4.10.0"},
# {:circuits_uart, "~> 1.4"},
{:jason, "~> 1.2"},
{:meeseeks, "~> 0.15.1"},
{:decimal, "~> 2.0"},
{:tesla, "~> 1.3"},
{:castore, "~> 0.1.0"},
# {:rustler, git: "git://github.com/rusterlium/rustler.git" branch: "master", sparse: "rustler_mix"},
{:rustler, "~> 0.22.0-rc.1", override: true}
]
end
0
dimitarvp
I’d try both things:
- Use the commented out line in your
mix.exs:
{:rustler, git: "git://github.com/rusterlium/rustler.git" branch: "master", sparse: "rustler_mix"},
- Put this into your
Cargo.tomlas @maciejgryka showed:
rustler = {git = "git://github.com/rusterlium/rustler.git", branch="master"}
7
myobie
(Gah, I’m sorry to double post, I messed up making an edit.)
You can override the version rustler is looking for with an ENV variable:
$ RUSTLER_NIF_VERSION=2.15 mix compile
This is the easiest way to make progress (I’ve found) without having to re-target any deps or anything.
Am I missing some downsides to doing this? I think rustler works just fine targeting the older nif version in my experience.
1
dimitarvp
The reason the approach above has been recommended is just one: rustler maintainers seem to be active again and we can expect a stable next release soon.
If not for that factor then I’d go with what you recommended.
0
