projects-dir.mk: Add BUILD_DEP_FLAVOURS_* #114

Merged

Jan Lindemann merged 1 commit from jan/feature/20260919-projects-dir-mk-add-build-dep-flavours into master 2026-09-19 20:44:38 +02:00 AGit

Conversation 0 Commits 1 Files changed 1 +13 -4

Jan Lindemann commented 2026-09-19 20:32:53 +02:00

Owner

Copy link

projects-dir.mk: Add BUILD_DEP_FLAVOURS_*

The top-level all, test, check, check-pre, and check-post targets invoke the build tool without --dep-flavours, so it falls back to the auto default and only resolves dependencies of the flavour "build". The build-order-% target, by contrast, already passes the run,build,test,release set via a single BUILD_ORDER_DEP_FLAVOURS variable. Planning and building therefore rely on different dependency flavours, and none of the targets can be tuned individually.

Introduce one flavour variable per target group, all of them defaulting to the run,build,test,release set:

• BUILD_DEP_FLAVOURS for all
• BUILD_DEP_FLAVOURS_LINT for check, check-pre, and check-post
• BUILD_DEP_FLAVOURS_TEST for test
• BUILD_DEP_FLAVOURS_ORDER, renamed from BUILD_ORDER_DEP_FLAVOURS, used by build-order-%

Split the combined all test check check-pre check-post rule into three rules so that each group passes its own --dep-flavours to the build tool. all, test, and the check targets now also resolve run, test, and release dependencies, as build-order already does, and each target's flavour set can be overridden independently.

Note that they all default the whole shebang: run,build,test,release. And this opens up the door to dependency cycles that don't exist with the subset of projects currently used. It's still better to ask for all and then cut down as needed instead of starting small.

#### projects-dir.mk: Add BUILD_DEP_FLAVOURS_* The top-level all, test, check, check-pre, and check-post targets invoke the build tool without --dep-flavours, so it falls back to the auto default and only resolves dependencies of the flavour "build". The build-order-% target, by contrast, already passes the run,build,test,release set via a single BUILD_ORDER_DEP_FLAVOURS variable. Planning and building therefore rely on different dependency flavours, and none of the targets can be tuned individually. Introduce one flavour variable per target group, all of them defaulting to the run,build,test,release set: - BUILD_DEP_FLAVOURS for all - BUILD_DEP_FLAVOURS_LINT for check, check-pre, and check-post - BUILD_DEP_FLAVOURS_TEST for test - BUILD_DEP_FLAVOURS_ORDER, renamed from BUILD_ORDER_DEP_FLAVOURS, used by build-order-% Split the combined all test check check-pre check-post rule into three rules so that each group passes its own --dep-flavours to the build tool. all, test, and the check targets now also resolve run, test, and release dependencies, as build-order already does, and each target's flavour set can be overridden independently. Note that they all default the whole shebang: run,build,test,release. And this opens up the door to dependency cycles that don't exist with the subset of projects currently used. It's still better to ask for all and then cut down as needed instead of starting small.

Jan Lindemann added 1 commit 2026-09-19 20:32:53 +02:00

projects-dir.mk: Add BUILD_DEP_FLAVOURS_* ... 0c4a69bd9a

The top-level all, test, check, check-pre, and check-post targets invoke
the build tool without --dep-flavours, so it falls back to the auto default
and only resolves dependencies of the flavour "build". The build-order-%
target, by contrast, already passes the run,build,test,release set via a
single BUILD_ORDER_DEP_FLAVOURS variable. Planning and building therefore
rely on different dependency flavours, and none of the targets can be tuned
individually.

Introduce one flavour variable per target group, all of them defaulting to
the run,build,test,release set:

- BUILD_DEP_FLAVOURS for all
- BUILD_DEP_FLAVOURS_LINT for check, check-pre, and check-post
- BUILD_DEP_FLAVOURS_TEST for test
- BUILD_DEP_FLAVOURS_ORDER, renamed from BUILD_ORDER_DEP_FLAVOURS, used by
  build-order-%

Split the combined all test check check-pre check-post rule into three
rules so that each group passes its own --dep-flavours to the build tool.
all, test, and the check targets now also resolve run, test, and release
dependencies, as build-order already does, and each target's flavour set
can be overridden independently.

Note that they all default the whole shebang: run,build,test,release. And
this opens up the door to dependency cycles that don't exist with the
subset of projects currently used. It's still better to ask for all and
then cut down as needed instead of starting small.

Signed-off-by: Jan Lindemann <jan@janware.com>
Assisted-by: unsloth/Qwen3.8-27B-GGUF:Q4_K_M with pi.dev v0.85.1

Jan Lindemann scheduled this pull request to auto merge when all checks succeed 2026-09-19 20:32:55 +02:00

Jan Lindemann merged commit 0c4a69bd9a into master 2026-09-19 20:44:38 +02:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

janware/jw-pkg!114

No description provided.