Preprocessing with actions and future syntax cannot be used in conjunction with (instrumentation ...)
Open
Nobody has claimed this yet.
preprocessing
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
Desired Behavior
I would like to be able to use action together with instrumentation. I am compiling OCaml extracted from Coq and want to profile it. Unfortunately, due to https://github.com/coq/coq/issues/6614 the generated code needs to be patched. I do not see why combining both stanzas should not be possible.
Example
(library
(name extracted)
(preprocessor_deps CRelationClasses.mli.patch patch.sh)
(preprocess (per_module
((action (run coq/extracted/patch.sh %{input-file})) CRelationClasses)
))
(public_name cerberus.coq)
(libraries zarith coq-core.kernel)
(wrapped false)
(flags (:standard -rectypes -w -27-32-33-39-67-37-20-34))
(instrumentation (backend landmarks))
)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the example Dune library stanza in this issue and trace how per-module preprocess actions and instrumentation are validated or combined. Reproduce the provided configuration, then confirm that both preprocessing with action and instrumentation can be used together without breaking the generated build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100