-
Notifications
You must be signed in to change notification settings - Fork 410
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[coq] Preliminary support for split native compilation
Coq 8.14 can generate native files independently from .vo file generation by using a new `coqnative` compiler, which will do the `.vo -> .cmxs` translation. This allows Dune to have a simpler rule setup, as it is always possible to rely on coqnative to compile native files, as opposed to before where native file generation was controlled by a Coq-level configure flag. The new rule setup is enabled for `(lang coq 0.4)`, and we provide a couple of configuration options in the `mode` field via a couple of optional fields: ```lisp (coq.theory ... (mode (native (package pkg) (profile p1 ... pn)))) ``` The first field, `(package )` allows to override the package under which native files for the corresponding theory will be installed. This is useful for packagers willing to split the native compilation under a different package, given that it can be extremely resource-intensive. The default for this setting is the same package name. The second field controls under which profiles Dune will setup the native build rules; the default for this setting is `release`, so Dune will skip Coq's native compilation when in `dev` mode. `(mode vo)` is still accepted, in case developers would like to completely disable native generation. TODO: take into account the `(package field)` for `native` , to be implemented in the next commit. Signed-off-by: Emilio Jesus Gallego Arias <[email protected]>
- Loading branch information
Showing
21 changed files
with
360 additions
and
58 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.