-
Notifications
You must be signed in to change notification settings - Fork 28
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
Using ppx_expect when there is no libc #15
Comments
ppx_expect is in theory usable in Mirage since it strips the code in the released binaries; but for now it causes some cross-compilation issues because of C stubs that rely on POSIX APIs. So for now let's do without it! See janestreet/ppx_expect#15
I think this is related to the discussion in ocaml/dune#897, but please correct me if I'm wrong. |
Whoops, completely missed this issue. We are now monitoring github issues with our internal review tool, so we should follow up more promptly in the future. So thinking again about this, as long as you are happy to keep an opam dependency on |
It's great to see that a solution is possible. In the context of Mirage and opam metadata, I think that depending on It seems OK to wait for the solution described in ocaml/dune#897 (comment). |
Hello,
This is a bit of an open question - sorry for the large scope.
I'm trying to build a library that has expect tests as part of a mirage unikernel.
I'm not interested in running the tests (just stripping the test nodes would work), but at the moment it's preventing compilation because
ppx_expect
has some C stubs that refer to some functions that are not available in mirage, likedup
ordup2
.How do you think we could support this use case?
Thanks!
The text was updated successfully, but these errors were encountered: