-
Notifications
You must be signed in to change notification settings - Fork 141
-
Notifications
You must be signed in to change notification settings - Fork 141
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
Missing class path under MacOS for Java FFI #948
Comments
Hi, could you share your
And the tree:
For the path of the bash file it seems you named your executable |
Sure, the cabal file:
And the tree:
The executable is named test and there is a file Thanks for helping! |
The cabal file and the tree seems to be correct. In theory the script should not add the class file to classpath, it should be inside In my windows env i've tested it succesfully and my jar contents are:
My package eta.first.test;
import java.nio.file.Files;
import java.nio.file.Paths;
public class Utils {
/* This helper method lets us avoid variadic arguments which
are a bit cumbersome to work with in Eta. */
public static void createFile(String path) throws Exception {
Files.createFile(Paths.get(path));
}
} |
The class file is not in
My |
Mmm, i wonder if it could be a mac (and linux?) specific issue, maybe @rahulmutt could help us to reproduce it |
@drever Perhaps you're using a version of Java > 9? There was a bug fix recently and there should be a release pretty soon that includes the fix. |
@drever Eta v0.8.6b5 is out - can you try it again and let me know if you still face the same issue? |
Description
I'm trying to get the FFI to Java running on MacOS 10.14.3, using the documentation here. The class
eta.first.Utils
is not found.Expected Behavior
The java function should be called from eta.
Actual Behavior
Possible Fix
The bash file
dist/build/eta-0.8.6.4/test-0.1.0.0/x/test/build/test/test
starts the jvm with the corresponding class path. Adding the path to the class files manually fixes the problem.Steps to Reproduce
etlas run
Your Environment
First installation
etlas version 1.5.0.0
MacOS 10.14.3
The text was updated successfully, but these errors were encountered: