-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add generic support for staging helix payloads
For a directory specified as a helix correlation payload, the helix tasks will attempt to write a `.payload` file to the directory. But if the directory is not writable then we need to stage the payload in a writable location, before passing the path to helix. For example, if we have `wasi-sdk` installed on the system as: `WASI_SDK_PATH=/usr/local/wasi-sdk` .. then we can stage it by copying to `artifacts/obj/helix-staging/wasi-sdk`, and then using that staging path for the helix correlation payload. This was already being done for `EMSDK`, and `WasiSdk` in two separate targets. And now needs to be done for `wasmtime` also. Instead of having completely separate targets for all this, add a new mechanism to specify helix dependencies to stage. For example: ```xml <ItemGroup> <HelixDependenciesToStage Condition="'$(NeedsWasmtime)' == 'true'" SourcePath="$(WasmtimeDir)" Include="$(WasmtimeDirForHelixPayload)" /> </ItemGroup> ``` .. and the payload can use specified as ```xml <HelixCorrelationPayload Include="$(WasmtimeDirForHelixPayload)" Destination="wasmtime" Condition="'$(NeedsWasmtime)' == 'true'" /> ```
- Loading branch information
Showing
3 changed files
with
80 additions
and
45 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters