Skip to content

Alternative implementation approach #1

@gasche

Description

@gasche

You shouldn't need to fork the whole codebase, because ocamlbuild provides ocamlbuild_pack.cmo that contains all the modules and the logic. So you should be able to just write your rmlbuild_specific.ml file (opening Ocamlbuild_pack in front), then fork the main.ml file, and then write a tiny rmlbuild.ml that just call the main () function, like ocamlbuild.ml does:

open Ocamlbuild_pack
Ocamlbuild_unix_plugin.setup ();
Rml_main.main ()

I think that doing this would minimize synchronization woes for you if the ocamlbuild sources evolve.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions