You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mentioned to use target as darwin-x64-all-clusters-no-ble-asan-clang for macOS.
This results in
Error: Invalid value for '--target': 'darwin-x64-all-clusters-no-ble-asan-clang' is not a valid target name.
It seems the correct target name is actually darwin-arm64-all-clusters-no-ble-asan-clang (x64 --> arm64)
This seems potentially trivial, although darwin-x64 is used in a number of places in yaml files. Not sure if it was changed somewhere along the way, just not everywhere? Or if there is otherwise a proper disctinction. Perhaps @bzbarsky-apple or @jtung-apple have insight?
Platform
darwin
Anything else?
No response
The text was updated successfully, but these errors were encountered:
It seems the correct target name is actually darwin-arm64-all-clusters-no-ble-asan-clang (x64 --> arm64)
That depends on whether you're on an Intel or ARM Mac, right?
CI uses darwin-x64 because the things it's running on have Intel processors. If you're on an Intel mbp/air/whatever, darwin-x64 is the right thing. If you're on an M1/2/3/etc laptop darwin-arm64 is the right thing.
@ndyck14 I agree the docs should be clearer about this. Do you want to fix them up, or should I do it?
Documentation issues
instructions provided on https://github.com/project-chip/connectedhomeip/tree/master/examples/all-clusters-app/linux
mentioned to use target as
darwin-x64-all-clusters-no-ble-asan-clang
for macOS.This results in
It seems the correct target name is actually
darwin-arm64-all-clusters-no-ble-asan-clang
(x64 --> arm64)This seems potentially trivial, although darwin-x64 is used in a number of places in yaml files. Not sure if it was changed somewhere along the way, just not everywhere? Or if there is otherwise a proper disctinction. Perhaps @bzbarsky-apple or @jtung-apple have insight?
Platform
darwin
Anything else?
No response
The text was updated successfully, but these errors were encountered: