Skip to content

API shape + rule naming for the native/common rules #1684

Description

@cgruber

Child of #1682. Type: decision. See anchor Section 4.

The one decision that unblocks everything downstream: #1351's explicitly-deferred TODO
("decide if a separate rule is needed for klibs or fit it into existing platform-specific
rules"
).

Options (full discussion in anchor Section 4):

My recommendation: (A) as the core, with target selection by --platforms (the
configuration half of (B)), and a later kt_multiplatform_library / metadata-klib path for
expect/actual. Grounding: platform klibs are target-tagged (verified in the prototype:
manifests read native_targets=macos_arm64 vs linux_x64), so a platform klib isn't a single
portable artifact; a dedicated rule models that honestly.

Naming: #1351 used kt_library for the neutral klib rule; the prototype uses
kt_native_library. We should converge on one. (I lean kt_library actually, despite my prototype)

Asking for: pick A/B/C and the names.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

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