5 commits

Author	SHA1	Message	Date
Viktor Hofer	bdd5d32572	Use NetTool* TFM properties for msbuild tasks (#98098) ... ... and remove the custom defined ones.	2024-02-07 17:21:30 +01:00
Ankit Jain	a36a860f74	[wasm] Extract src/mono/browser from src/mono/wasm (#95940) ... * [wasm] Extract src/mono/browser from src/mono/wasm, and update to track changes * [wasm] Makefile - update to remove some unrelated targets * [wasm] Rename wasm.proj to browser.proj - feedback from @ maraf * Add the renamed browser.proj * address review feedback from @ maraf * review feedback from @ pavelsavara * address review feedback from @ maraf	2023-12-19 10:03:41 -05:00
Alexander Köplinger	52f7d32198	Use GenerateFileFromTemplate task from arcade instead of repo copy (#96049) ... They were both based on some aspnetcore build tooling, the only difference in the arcade one is that is uses key=value strings for the replacement properties instead of msbuild items. Also fix an issue in workloads-testing.targets where we didn't use a separate MSBuild evaluation for the Restore task which meant that the build tasks weren't loaded in the Pack task.	2023-12-15 17:48:47 +01:00
Ankit Jain	a128c1503a	[wasm/wasi] Consolidate build targets (#95775) ... * [wasm/wasi] Consolidate build targets Current state of build files: ``` wasm: WasmApp.props, WasmApp.targets, WasmApp.Native.targets wasi: WasiApp.props, WasiApp.targets, WasiApp.Native.targets `` The wasm, and wasi build have lot of shared code but that is not representative in the actual files, since the wasi targets started life as a quick-copy-comment-out-bits of the wasm targets. This commit consolidates these into: ``` common: WasmApp.Common.props, WasmApp.Common.targets wasm : WasmApp.props, WasmApp.targets wasi : WasiApp.props, WasiApp.targets ``` ## `WasmApp.Common.{props,targets}` This has all the common parts of the build for browser-wasm, and wasi, and includes bits from `WasmApp.{props,targets}`, and `WasmApp.Native.{props,targets}`. - The top level target remains the same - `WasmBuildApp`. - There are a few "public" targets that can be hooked into: - `PrepareInputsForWasmBuild` - `WasmGenerateAppBundle` - `PrepareForWasmBuildNative` - `WasmLinkDotNet` - all these public targets have corresponding `*DependsOn` properties which can be used for extending the build note: this commit does not add a public target for AOT, but it might be added in future. ## WasmApp.{props,targets} This is for `browser-wasm` projects. The file might be renamed in future. ## WasiApp.{props,targets} This is for `wasi-wasm` projects. `ILStrip` becomes usable as a feature for `wasi-wasm` because of this consolidation. * [wasi] WBT: Use TestOutputWrapper * [wasm] WBT: Track target name changes * [wasi] WBT: Add new tests * cleanup * cleanup * address feedback * address feedback	2023-12-11 14:45:58 -06:00
Ankit Jain	ef439346a2	[wasi] Add wasi-experimental workload, wasiconsole template, and Wasi.Build.Tests (#81849) ... * EmitWasmBundleObjectFile: Capture any clang output/errors * [wasi] Add wasiconsole template * [wasi] Add wasmtime support for WasmAppHost * [wasi] Add wasi-experimental workload - And Microsoft.NET.Runtime.WebAssembly.Wasi.Sdk * [wasi] Add Wasi.Build.Tests * [wasi] cleanup * [wasi] liveBuilds.targets - add dotnet.wasm, and other files * Add CI support for Wasi.Build.Tests * fix build * Link required libc++*.a from wasi-sdk * Address earlier review feedback from @pavelsavara	2023-02-23 18:36:37 -05:00