-
Notifications
You must be signed in to change notification settings - Fork 232
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
Why do our binaries include ocamlopt and ocamlrun? Are they really needed? Are we legally allowed to redistribute them? #234
Comments
Note that it's possible to get OCaml under the BSD license by joining the Caml Consortium; http://caml.inria.fr/consortium/. (Microsoft is already a member) |
@avsm This is good to know, thanks a lot. My impression is that we don't need to bundle OCaml with our binaries anyway. In fact we just removed them from the latest release. |
Nope, it shouldn't be necessary. I'm taking a look at adding an OPAM package for Fstar that'll make it even easier. Just needs Z3 first (ocaml/opam-repository#3298). |
Having an OPAM package for Fstar would be great, of course. Please let us know when there is something with which we can help. |
It is no longer necessary in the current setup. |
OCaml on windows is still quite broken: |
The
make package
target from theMakefile
insrc/ocaml-output
includes this:@ad-l Why are these OCaml binaries sometimes copied in (and sometimes not, since the hardcoded path seems very fragile)? Are they needed for anything?
If they are really needed we would need to think more seriously about licensing issues. OCaml is released under the rather non-standard Q Public License:
https://ocaml.org/docs/license.html
https://en.wikipedia.org/wiki/Q_Public_License
The text was updated successfully, but these errors were encountered: