-
Notifications
You must be signed in to change notification settings - Fork 53
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
fix for ocamlbuild's pack+ocamlfind handling #144
base: master
Are you sure you want to change the base?
Conversation
ocamlbuild should pass -package(...) flags to ocamlfind when building a -pack-ed file, see ocaml/opam-repository#11628 (comment)
Binaries in <bench/*>, <tests/*> depend on the runtime libraries within ppx_sexp_conv and ocplib-endian. The packed modules <src/nocrypto.cm{x,o}> also depend on the package ppx_sexp_conv: its presence at pack-creation time influences the generated .cmi interface, see ocaml/opam-repository#11628 (comment) Note: the package ppx_sexp_conv.runtime-lib would suffice, but it is only available as such under recent ppx_sexp_conv versions, so its explicit use would make the build description (needlessly) incompatible with older ppx_sexp_conv versions.
hmm, IIUC, this makes |
|
Wouldn't |
You should test this, but I think from the META file that the .expander dependency should only exists under the |
Ah, indeed it doesn't get linked. (tested by adding |
@gasche In the |
ppx_sexp_conv v0.11.0 compiles successfully, but contains an undesired dependency on base, and is thus still marked as conflicting. This is fixed in ppx_sexp_conv v0.11.1. This commit submits @gasche's fixes from mirleft/ocaml-nocrypto#144
ppx_sexp_conv v0.11.0 compiles successfully, but contains an undesired dependency on base, and is thus still marked as conflicting. This is fixed in ppx_sexp_conv v0.11.1. This commit submits @gasche's fixes from mirleft/ocaml-nocrypto#144 and @diml's fixes from mirleft/ocaml-nocrypto#146
ppx_sexp_conv v0.11.0 compiles successfully, but contains an undesired dependency on base, and is thus still marked as conflicting. This is fixed in ppx_sexp_conv v0.11.1. This commit submits @gasche's fixes from mirleft/ocaml-nocrypto#144 and @diml's fixes from mirleft/ocaml-nocrypto#146
ppx_sexp_conv v0.11.0 compiles successfully, but contains an undesired dependency on base, and is thus still marked as conflicting. This is fixed in ppx_sexp_conv v0.11.1. This commit submits @gasche's fixes from mirleft/ocaml-nocrypto#144 and @diml's fixes from mirleft/ocaml-nocrypto#146
ppx_sexp_conv v0.11.0 compiles successfully, but contains an undesired dependency on base, and is thus still marked as conflicting. This is fixed in ppx_sexp_conv v0.11.1. This commit submits @gasche's fixes from mirleft/ocaml-nocrypto#144 and @diml's fixes from mirleft/ocaml-nocrypto#146
This PR fixes the issue that causes the build failure discussed in
ocaml/opam-repository#11628 (comment)
and
#143
I have another branch v0.5.4-ocamlbuild-pack against the
v0.5.4
tag, where the_tags
changes are slightly different.