this repo has no description
1opam-version: "2.0"
2maintainer: "Drup <drupyog@zoho.com>"
3authors: "Drup <drupyog@zoho.com>"
4license: "ISC"
5homepage: "https://github.com/Drup/bytepdf"
6bug-reports: "https://github.com/Drup/bytepdf/issues"
7dev-repo: "git+https://github.com/Drup/bytepdf.git"
8
9depends: [
10 "ocaml" {>= "4.03"}
11 "dune" {>= "1.1"}
12 "containers" {>= "0.12"}
13 "bos"
14 "cmdliner"
15 "obytelib" {>= "1.4" & < "1.6"}
16 ("camlpdf" {< "2.4"} & "ocaml" {< "4.08"}) | ("camlpdf" & "ocaml" {>= "4.08"}) # Transitively depends on bigarray
17]
18build: [
19 ["dune" "subst"] {dev}
20 ["dune" "build" "-p" name "-j" jobs]
21]
22synopsis: "Tool to create PDFs that are also OCaml bytecodes"
23description: """
24The `bytepdf` tool allows you to take a PDF `foo.pdf` and an OCaml bytecode `foo.byte` and merges them into a file that is both a valid PDF and a valid bytecode.
25
26```
27bytepdf --ml foo.byte --pdf foo.pdf -o bar.pdf
28```
29
30The resulting file can both be read as a pdf and executed by the ocaml interpreter:
31
32```
33open bar.pdf
34ocamlrun bar.pdf
35```
36
37Furthermore, if you open the PDF with Acrobat Reader, the PDF will contain the OCaml bytecode as a file attachment. For more details, you can read the help. For an explanation of how this work, consider looking at [this abstract](abstract.pdf).
38The only current limitation is that the bytecode should not
39have been statically linked with C code."""
40url {
41 src:
42 "https://github.com/Drup/bytepdf/releases/download/0.1/bytepdf-0.1.tbz"
43 checksum: [
44 "sha256=abe48c195143f6cfd57ff2860ae9465d73b883b4911cd7eb22332f12863f6380"
45 "md5=5480d78b88229a03019dad0d023c3162"
46 ]
47}