-
Notifications
You must be signed in to change notification settings - Fork 118
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
Elixir: Relative path to extism/rust fails to compile #343
Comments
@code0100fun thanks for reporting, are you seeing this from the current package from hex.pm? This has popped up before, will try to come up with a fix this week. |
Yes, I'm seeing it in |
Still working out the best overall fix for this over here: #345 But I submitted a manually fixed version on |
Can confirm |
Published this fix as 0.3.2: #343 going to disconnect this rust project for the time being. If we want to publish a new elixir client with the new runtime then we must wait until the runtime hit's crates.io
Published this fix as 0.3.2: extism/extism#343 going to disconnect this rust project for the time being. If we want to publish a new elixir client with the new runtime then we must wait until the runtime hit's crates.io
extism/elixir/native/extism_nif/Cargo.toml
Line 14 in 8d76cf0
The relative path in the
Cargo.toml
assumes the dependency was being loaded from a relative location to the entire extism repo not the publishedelixir/
directory.Steps to reproduce:
The text was updated successfully, but these errors were encountered: