package b0
Software construction care
Install
Dune Dependency
Authors
Maintainers
Sources
b0-0.0.0.tbz
sha256=dadde8cfa62be9dabd805fc190b415427b4699ffe3458c153e2f3f9cc5c9b9b4
md5=f96ac96fb0182f2b97dbe9ded452544b
doc/b0.care/B0_trace/Compilation_database/index.html
Module B0_trace.Compilation_database
JSON compilation database.
Output build operation spawns in JSON compilation database format (see also here).
The format is a bit underpowered (see also the discusion in the merlin issue tracker here) and doesn't exactly match B0's build model here are a few notes on the treatment:
- The
file
field. B0's operations do not identify a "main source" processed by a step. For now we use the first element ofOp.reads
TODO maybe we should spell out this convention inMemo
. - The
output
field. B0's operations support multiple writes. If multiple files are written we repeat the command for each write. We add an numberedid
field to indicate that this is the same command. - No specification of the environment, we add it under an
env
key as an array of strings. - We never generate
command
, we only usearguments
.
JSON compilation database
val of_ops : B00.Op.t list -> B0_web.Jsong.t
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>
On This Page