ocaml/dune

Controlling flags for ocamldep (e.g. for specifying keywords)

Open

#11,419 opened on Jan 30, 2025

View on GitHubContributor guide
 (12 comments) (0 reactions) (0 assignees)OCaml (478 forks)github user discovery
buildgood first issuehelp wanted

Repository metrics

Stars
 (1,882 stars)
PR merge metrics
 (Avg merge 1d 20h) (345 merged PRs in 30d)

Description

There will likely be a need to allow specification of flags to ocamldep, depending on the resolution of ocaml/ocaml#13764. Currently, as per the docs, flags can only be specified for ocamlc and ocamlopt.

Alternatively, there could be a special keywords construct that is applied to all tools that use the ocaml lexer/parser version 5.3.0 or later. However, this might collide with keywords being specified in flags.

Contributor guide

Research direction
Investigate the referenced issue ocaml/ocaml#13764 to understand the need for ocamldep flags. Examine how dune currently handles flags for ocamlc and ocamlopt, and design a similar mechanism for ocamldep. Consider whether a separate `keywords` construct is more appropriate and how to avoid conflicts with existing `flags`.
Tech stack
None
Domain
build system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
OCamlDune
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45