@@ -18,10 +18,10 @@ Here are some of the `Zig.Sdk` highlights:
1818 [ Clang] ( https://clang.llvm.org ) . So, whichever language you prefer, ` Zig.Sdk `
1919 has you covered.
2020* ** Cross-compilation:** Thanks to the Zig compiler's excellent cross-targeting
21- support, you can build native code for a variety of target platforms no matter
22- what platform you are on. Gone are the days of having to do overly complicated
23- cross toolchain setup, or resorting to building on multiple platforms for
24- releases. Cross-compilation is a first-class citizen in ` Zig.Sdk ` .
21+ support, cross-compilation is a first-class citizen in ` Zig.Sdk ` . Gone are the
22+ days of having to do overly complicated cross toolchain setup, or resorting to
23+ building on multiple platforms for releases - just type ` dotnet build ` to
24+ compile for all targets supported by your project .
2525* ** Binary emulator support:** When cross-compiling, ` Zig.Sdk ` will look at the
2626 host and target platforms and try to pick an appropriate emulator. In the
2727 majority of cases, this allows you to run and unit test the foreign binary.
@@ -37,10 +37,10 @@ Here are some of the `Zig.Sdk` highlights:
3737 expected, enabling a rapid development loop.
3838* ** Sensible NuGet packaging:** Out of the box, ` dotnet pack ` with ` Zig.Sdk `
3939 will produce NuGet packages containing cross-built binaries for all platforms
40- that your project declares support for . Also, your public C and C++ header
41- files will be bundled, as will your Zig source code. This makes the resulting
42- NuGet package easy to consume both in ` Microsoft.NET.Sdk ` projects and in
43- other ` Zig.Sdk ` projects.
40+ that your project supports . Also, your public C and C++ header files will be
41+ bundled, as will your Zig source code. This makes the resulting NuGet package
42+ easy to consume both in ` Microsoft.NET.Sdk ` projects and in other ` Zig.Sdk `
43+ projects.
4444* ** Multi-project solutions:**
4545 [ Soon™.] ( https://github.com/alexrp/zig-msbuild-sdk/issues/8 )
4646* ** Easy to use:** Just add an entry to your ` global.json ` , and create a project
@@ -244,10 +244,11 @@ as sensible for historical reasons.
244244#### Cross-Compilation
245245
246246* ` RuntimeIdentifier ` : Specifies the runtime identifier (i.e. platform) to
247- target. Defaults to the runtime identifier of the current platform. Usually
248- specified by the user as e.g. ` dotnet build -r linux-x64 ` .
247+ target. When unset, ` Build ` and ` Clean ` will run for all runtime identifiers
248+ specified in ` RuntimeIdentifiers ` . Usually specified by the user as e.g.
249+ ` dotnet build -r linux-x64 ` . Unset by default.
249250* ` RuntimeIdentifiers ` : A semicolon-separated list of runtime identifiers that
250- your project supports. All targets on this list will be cross-compiled when
251+ the project supports. All targets on this list will be cross-compiled as
251252 necessary. Defaults to all targets that the Zig compiler has known-good
252253 support for.
253254* ` UseEmulator ` (` true ` , ` false ` ): Enable/disable usage of an appropriate binary
0 commit comments