(rule (target libvpx.a) (deps (source_tree libvpx-src)) (action (progn (chdir libvpx-src (progn (run ./configure --target=x86_64-linux-gcc ; Change per host --disable-shared --enable-static --disable-examples --disable-tools --disable-docs --disable-unit-tests --size-limit=4096x2160 --enable-postproc --enable-vp9-postproc --enable-runtime-cpu-detect --prefix=%workspace_root/_build/default/libvpx/install) (run make -j4) (run make install))) (copy %workspace_root/_build/default/libvpx/install/lib/libvpx.a libvpx.a)))) Finally, create a dune file in your project’s root or a stubs directory:
(rule (target libvpx-commit.tar.gz) (action (run curl -L https://github.com/webmproject/libvpx/archive/v1.13.1.tar.gz -o %target))) (rule (target extracted) (deps libvpx-commit.tar.gz) (action (progn (run tar -xzf libvpx-commit.tar.gz) (run mv libvpx-1.13.1 libvpx-src) (write-file extracted "done")))) Now, we invoke libvpx’s own build system but redirect the output to Dune’s artifact cache. The trick is to set the --prefix and --libdir to Dune’s _build/default/libvpx/install . dune libvpx
Try it yourself: Clone this example repository (hypothetical) and run dune build @install . You’ll have a VP9 encoder binary that is completely independent of your system’s multimedia libraries. Have you integrated libvpx with an unconventional build system? Share your war stories in the comments below. (rule (target libvpx