diff options
| author | aidanfnv <aidanf@nvidia.com> | 2025-10-01 13:07:55 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-01 20:07:55 +0000 |
| commit | a43ac0053eb49fde3329cc7fdc7f60f45e502704 (patch) | |
| tree | 8c1304b57e4b55cae2b648b2988bcf1b4ee18cb8 /examples/cpu-com-example | |
| parent | 5793b6d864b572e464dd5e17dc842e99d13d310d (diff) | |
Re-add Windows cross-compile setup from release workflow (#8580)
For #8578
This re-adds the cross-compile target setup step for Windows releases
that was erroneously removed in #8470, which made aarch64 releases build
x64 binaries.
The flow should be:
- setup MSVC for host arch
- build generators with cmake
- setup MSVC for cross-compile target arch
- build slang
Based on the description of #8470, it seems that the cross-compile MSVC
step was mistaken as a duplicate for the host MSVC step and removed for
being seemingly redundant.
Diffstat (limited to 'examples/cpu-com-example')
0 files changed, 0 insertions, 0 deletions
