build: honor CARGO_TARGET_DIR and DX_ENV in remaining Makefile targets #106

Merged
omarz merged 1 commit from fix/makefile-target-dir-and-dx-env into development 2026-04-29 12:05:13 +00:00
Member

Two follow-ups to existing build-system patterns the Makefile already
declared but didn't apply consistently:

  1. install / installdev: cp lines hardcoded target/{release,debug}/...
    instead of using the CARGO_TARGET_DIR ?= target variable already
    defined at line 17 (and used by the WASM_*_OUTPUT paths). With
    Hero's standard CARGO_TARGET_DIR=~/hero/build/cargo, cargo built
    into the override path while cp still looked under ./target and
    failed with "No such file or directory". No behavior change when
    CARGO_TARGET_DIR isn't set.

  2. web / dev / desktop: missed prepending $(DX_ENV) (which clears
    RUSTC_WRAPPER so sccache stops treating dx as the compiler — see
    2b97cdf). Same sccache "Compiler not supported" failure that
    2b97cdf fixed for build / build-wasm was hitting the dev-server
    targets. No behavior change when RUSTC_WRAPPER isn't set.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

Two follow-ups to existing build-system patterns the Makefile already declared but didn't apply consistently: 1. install / installdev: cp lines hardcoded `target/{release,debug}/...` instead of using the `CARGO_TARGET_DIR ?= target` variable already defined at line 17 (and used by the WASM_*_OUTPUT paths). With Hero's standard `CARGO_TARGET_DIR=~/hero/build/cargo`, cargo built into the override path while cp still looked under ./target and failed with "No such file or directory". No behavior change when CARGO_TARGET_DIR isn't set. 2. web / dev / desktop: missed prepending `$(DX_ENV)` (which clears RUSTC_WRAPPER so sccache stops treating dx as the compiler — see 2b97cdf). Same sccache "Compiler not supported" failure that 2b97cdf fixed for `build` / `build-wasm` was hitting the dev-server targets. No behavior change when RUSTC_WRAPPER isn't set. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
build: honor CARGO_TARGET_DIR and DX_ENV in remaining Makefile targets
All checks were successful
Build and Test / build (pull_request) Successful in 3m18s
7521d420fb
Two follow-ups to existing build-system patterns the Makefile already
declared but didn't apply consistently:

1. install / installdev: cp lines hardcoded `target/{release,debug}/...`
   instead of using the `CARGO_TARGET_DIR ?= target` variable already
   defined at line 17 (and used by the WASM_*_OUTPUT paths). With
   Hero's standard `CARGO_TARGET_DIR=~/hero/build/cargo`, cargo built
   into the override path while cp still looked under ./target and
   failed with "No such file or directory". No behavior change when
   CARGO_TARGET_DIR isn't set.

2. web / dev / desktop: missed prepending `$(DX_ENV)` (which clears
   RUSTC_WRAPPER so sccache stops treating dx as the compiler — see
   2b97cdf). Same sccache "Compiler not supported" failure that
   2b97cdf fixed for `build` / `build-wasm` was hitting the dev-server
   targets. No behavior change when RUSTC_WRAPPER isn't set.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
omarz merged commit bb48671eea into development 2026-04-29 12:05:13 +00:00
omarz deleted branch fix/makefile-target-dir-and-dx-env 2026-04-29 12:05:14 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
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
lhumina_code/hero_os!106
No description provided.