view release on metacpan or  search on metacpan

lib/App/hopen/Conventions.pod  view on Meta::CPAN

a build system to perform a particular action on a file belonging to a
particular language.

A tool is an L<App::hopen::G::Cmd>, so may interact with the current generator
(L<App::hopen::BuildSystemGlobals/$Generator>).  Moreover, the generator will
get a chance to visit the op after it is processed.

Maybe TODO:

    - Each Generator must specify a list of Content-Types (media types)
        it can consume.  Each Tool must specify a specific content-type
        it produces.  Mismatches are an error unless overriden on the
        hopen command line.

=head2 Toolchain

TODO?

    - permit loading any number of tools/toolchains
    - The Generator specifies a default list of tools rather than a
        single default toolchain.
    - add G::ToolOp to invoke tools.  A ToolOp will take a language
        and an opcode and invoke a corresponding Tool.  E.g., a GNU C
        Tool will generate command-line options for gcc-style command lines.
    - Only one Tool may be loaded for each (language, opcode) pair.
        Otherwise the build would be ambiguous.
    - In Conventions, define the formats for languages and opcodes.

Maybe TODO:

    - Each Generator must specify a list of Content-Types (media types)
        it can consume.  Each Tool must specify a specific content-type
        it produces.  Mismatches are an error unless overriden on the
        hopen command line.

=head2 Phases

App::hopen::Phase - Namespace for hopen phases.

The specific phases in hopen live under C<App::hopen::Phase>.  The
current phases are: