Skip to content

Code generation #179

@John-Colvin

Description

@John-Colvin

I have a build with a tangled web of code-gen steps in it where you won't know what outputs you'll get (and therefore what inputs will be read for the next step, e.g. a command might read all the files in an output folder of the previous command) until you run them. The "main" build is a dub package, but that dub package needs to depend on the previous tangled web of code-gen steps.

How might I approach this with reggae?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions