You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-12Lines changed: 5 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,22 +40,15 @@ The built output is in `_build` but the final binary is symlinked `_build/src/in
40
40
41
41
While developing you can simply modify the `_tags` file which is what `rebuild uses to figure out what you depend on. See inside that file for more instructions.
42
42
43
-
Before publishing onto opam you'll need to edit your `opam` file so that you depend on a particular opam package and range of versions.
43
+
##### Releasing
44
44
45
-
In addition you may have to tweak the buildstep to recognize the dependency, by changing `build.ml` within the `pkg` folder. and add the following for you dependency:
46
-
```ocaml
47
-
...
48
-
OS.Cmd.run @@ Cmd.(
49
-
ocamlbuild % "-use-ocamlfind"
50
-
%% (v "-I" % "src")
51
-
%% (v "-pkg" % "[PACKAGE]") (* <---- only change is this line*)
52
-
%% of_list files)
53
-
...
54
-
```
45
+
Before publishing onto all you'll need to do is run `make release` to generate all of the files necessary for opam. Then you can follow the steps [here](https://opam.ocaml.org/doc/Packaging.html#GettingafullOPAMpackage).
46
+
47
+
If you've added extra opam dependencies you'll need to update the package.json under `opam > dependencies`. You can see all of the possible fields you can tweak on the [opam_of_packagejson](https://github.com/bsansouci/opam_of_packagejson) github.
55
48
56
49
Finally For your editor to pick up the dependency and fancy autocomplete etc. make sure to add the package in your `.merlin` file:
0 commit comments