Skip to content

Feature request: support in-project SDKs #294

Open

Description

@saviq-work

There's currently no good way to embed an sdkcraft definition in existing projects. A common SDK tree will look like:

.
├── hooks
│   └── setup-base
├── README.md
├── sdkcraft.yaml
└── tests
    ├── main
    │   └── launch
    │       ├── consumer.cpp
    │       ├── task.yaml
    │       └── workshop.yaml.in
    └── spread.yaml

5 directories, 7 files

At least hooks and sdkcraft.yaml need to be relocatable so this can coexist within the upstream source repo and reference source: ..

The .workshop/<sdk> could possibly be used here, with sdkcraft taking either the SDK name, or the full path, as argument.

Alternatively, following other *crafts, sdk/sdkcraft.yaml, .sdk/sdkcraft.yaml.

Activity

  1. saviq-work commented on Oct 5, 2026

    @saviq-work
    Author

    Snapcraft supports snap/ at least…

  2. jonathan-conder commented on Oct 6, 2026

    @jonathan-conder
    Contributor

    Yeah I'm not saying we can't do sdk/ or .sdk/, maybe we can also do this .git detection thing though

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

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