package b0
Software construction and deployment kit
Install
Dune Dependency
Authors
Maintainers
Sources
b0-0.0.5.tbz
sha512=00a6868b4dfa34565d0141b335622a81a0e8d5b9e3c6dfad025dabfa3df2db2a1302b492953bbbce30c3a4406c324fcec25250a00b38f6d18a69e15605e3b07e
doc/b0_b00_kit/B00_trace/Compilation_database/index.html
Module B00_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 : B000.Op.t list -> B00_serialk_json.Jsong.t
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>
On This Page