-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support OCaml 5 #10
Comments
I've been trying it out recently and everything seems to work fine. I'm not sure if there would be any subtle issues with OCaml 5. I am assuming that you're running in a single domain -- I don't know what happens when you go to the multiple domain case.
Edit: Installing in a switch directly does not work. It needs to be pinned. See comment below |
P.S. I tried to follow my own instructions above and I get a similar error you opened the ticket with :-) . Sorry, my bad. Here is the way I've been able to get this to work with OCaml 5: $ mkdir my_fresh_switch
$ cd my_fresh_switch
$ opam switch create . 5.0.0 -y
$ git clone https://github.com/fdopen/ppx_cstubs.git
$ cd ppx_cstubs
$ opam pin . -y
$ cd ..
# Now ppx_cstubs is available in this switch for OCaml code that might want to use it
$ mkdir <your-own-ocaml-project>
...
... There might be some issues with the |
Curious,
However, for the 0.7 release, the version constraints have been removed (1562e75) @fdopen It seems you are busy at the moment, would you be ok with me creating the PR? |
Yes, go ahead. |
The one in the opam repo has two version constraints which make it impossible to use with OCaml 5. The opam file in the ppx_cstubs repo at the 0.7 tag doesn't have them (https://github.com/fdopen/ppx_cstubs/blob/0.7.0/ppx_cstubs.opam). This PR removes the version constraint to fix this, see relevant discussion here fdopen/ppx_cstubs#10
ppx_cstubs
does not support OCaml 5.I tried installing with opam on a fresh OCaml 5 switch and got the following error:
Would be nice to use this going forward, the bitmask feature in particular is nice
The text was updated successfully, but these errors were encountered: