Skip to content

livery.extensions.cpp._language

livery.extensions.cpp._language

What the C and C++ languages tell the workshop about a package's files.

The answers a C or C++ package gives where a python package names modules: none, since other packages reach its code through headers and libraries, never an import path.

Nothing here answers the references query, so the layering phase reads no C or C++ source for references: a header of another member, included with no requirement on that member, goes unseen.

Functions:

Name Description
module_roots

Nothing: other packages reach C or C++ code through headers, not imports.

public_modules

Nothing: a C or C++ package has no importable API to verify.

module_roots

module_roots(package: Package) -> tuple[str, ...]

Nothing: other packages reach C or C++ code through headers, not imports.

A consumer names the package by its recipe or its CMake target, which the package's own build files declare.

Source code in packages/extensions/cpp/src/livery/extensions/cpp/_language.py
def module_roots(package: Package) -> tuple[str, ...]:
    """Nothing: other packages reach C or C++ code through headers, not imports.

    A consumer names the package by its recipe or its CMake target,
    which the package's own build files declare.
    """
    del package
    return ()

public_modules

public_modules(package: Package) -> tuple[str, ...]

Nothing: a C or C++ package has no importable API to verify.

Source code in packages/extensions/cpp/src/livery/extensions/cpp/_language.py
def public_modules(package: Package) -> tuple[str, ...]:
    """Nothing: a C or C++ package has no importable API to verify."""
    del package
    return ()