Skip to content

Commit

Permalink
Using dune build @check to build the project
Browse files Browse the repository at this point in the history
The current target `all` of the `Makefile` is a bit complicated as
we want to build only the codebase without running tests when we type
`make`. After looking for a better solution, I found this issue on the
`dune` GitHub (ocaml/dune#7203) explaining
we have to use `dune build @check` and `dune build` builds everything
by design.

I modify the `Makefile` accordingly.
Halbaroth committed Oct 13, 2023
1 parent b553807 commit 52aafcf
Showing 1 changed file with 3 additions and 6 deletions.
9 changes: 3 additions & 6 deletions Makefile
Original file line number Diff line number Diff line change
@@ -90,13 +90,10 @@ AB-Why3:
plugins:
$(DUNE) build $(DUNE_FLAGS) @$(PLUGINS_DIR)/all

# Alias to build all targets using dune
# Alias to build all the bytecode artefacts using dune
# Hopefully more efficient than making "all" depend
# on "lib" and "bin", since dune can
# parralelize more
all:
$(DUNE) build $(DUNE_FLAGS) @$(LIB_DIR)/all @$(BTEXT_DIR)/all \
@$(PARSERS_DIR)/all @$(BJS_DIR)/all @$(PLUGINS_DIR)/all
# on "lib" and "bin", since dune can parralelize more
all: dune build @check

# declare these targets as phony to avoid name clashes with existing directories,
# particularly the "plugins" target

0 comments on commit 52aafcf

Please sign in to comment.