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
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,8 +25,8 @@ The Z80 binaries used are slightly modified versions of the originals; the chang
25
25
26
26
Download the latest release and choose the variant you want to use:
27
27
28
-
***Portable:** Consists of multiple `.dll` files and runs on any platform having [the .NET Core Runtime 3.1](https://dotnet.microsoft.com/download/dotnet-core/3.1) installed.
29
-
***Framework-dependant:** Single file, platform-specific applications that also require the .NET Core Runtime 3.1 to be installed. This is the perhaps the most convenient variant for frequent use.
28
+
***Portable:** Consists of multiple `.dll` files and runs on any platform having [the .NET Runtime 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) installed.
29
+
***Framework-dependant:** Single file, platform-specific applications that also require the .NET Runtime 6.0 to be installed. This is the perhaps the most convenient variant for frequent use.
30
30
***Self-contained:** Single file, platform-specific applications that have the .NET Core Runtime built-in and thus have no dependencies (at the expense of much bigger file sizes). These may be convenient for casual usage, or if you just want to give it a try before installing the .NET Runtime.
31
31
32
32
Place the chosen variant in a PATH-accessible directory and then run
@@ -123,9 +123,9 @@ The `WINBUILD.BAT` script will use `cpm.exe` and the original `M80.COM` and `L80
123
123
124
124
## Building the wrappers
125
125
126
-
The `Shared` project has a `PublishProfiles` folder containing a `build.sh` script and several `.pubxml` files, each containing a publish profile for each of the variants. The script (for Linux, it works on Windows 10 with WSL too) uses the `dotnet` tool to generate all the variants in the `Release` folder in the root directory of the project, you can just run it to build all the variants or pass the name of a publish profile (filename without the `.pubxml`) as a single argument.
126
+
To build the wrappers you'll need [the .NET 6 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/6.0). The `Shared` project has a `PublishProfiles` folder containing a `build.sh` script and several `.pubxml` files, each containing a publish profile for each of the variants. The script (for Linux, it works on Windows 10 with WSL too) uses the `dotnet` tool (part of the .NET SDK) to generate all the variants in the `Release` folder in the root directory of the project, you can just run it to build all the variants or pass the name of a publish profile (filename without the `.pubxml`) as a single argument.
127
127
128
-
If you prefer a more IDE-centric approach for compilation, you can copy all the `.pubxml` files to the `Properties/PublishProfiles` directory of each project, then right-click the project in Visual Studio and select "Publish".
128
+
You can also use [Visual Studio 2022](https://visualstudio.microsoft.com) for compiling the wrappers: copy all the `.pubxml` files to the `Properties/PublishProfiles` directory of each project, then right-click the project in Visual Studio and select "Publish".
0 commit comments