Skip to content

Commit

Permalink
Updated build documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
Banbrytande committed Apr 6, 2023
1 parent fa2462c commit 0e6ea49
Showing 1 changed file with 39 additions and 0 deletions.
39 changes: 39 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,45 @@

## Building

#### SDK Versions

- .NET Standard Core 2.1
- .NET Framework 4.6 or higher

**Note:** Tested with Visual Studio 2019 with .NET 5.0

First, [pahkat](https://github.com/divvun/pahkat) needs to be built to your local directory.

`git clone https://github.com/divvun/pahkat.git`

**Important:** Divvun Manager does not talk to the language index itself. It only communicate locally running pahkat service. Pahkat is responsible to install and update languages. So, pahkat service should be up and running in your Windows's Services.

Open `pahkat-client-core` directory in a terminal and source env for the platform `$Env:CARGO_FEATURE_WINDOWS="true"` before `cargo build`. Make sure the build to succeed.

Second, you should clone the divvun manager repo in the same pahkat folder.

`git clone https://github.com/divvun/divvun-manager-windows.git`

Be sure `divvun-manager-windows` and `pahkat-client-core` share the same root directory.

Open `Divvun.Installer.sln` in Visual Studio 2019 and build only `Pahkat.Sdk` project from the solution explorer to generate `Pahkat.Sdk.dll` file before building the whole solution.

Finally, **Build > Build Solution (Ctrl-Shift-B)**

When you try to run `Divvun.Installer`, it's not going to work because some pseudolocales will need to be added to your registry. The simplest way to do this is to install [kbdi](https://github.com/divvun/kbdi) outside of pahkat directory.

`git clone https://github.com/divvun/kbdi.git` then `cargo build --release --target i686-pc-windows-msvc --bin kbdi`

After the build is succeeded. Come to `.\target\i686-pc-windows-msvc\release` and run `kbdi.exe language_enable nn-Runr` command.

If everything goes well, you can run `Divvun.Installer` and it should work just fine.

#### Troubleshot

You might end up with enabling old .Net SDKs in Windows Feature Panel.

### Old guide

Open in Visual Studio 2017, run build in Release.

In order for all supported locales to generate properly, some pseudolocales
Expand Down

0 comments on commit 0e6ea49

Please sign in to comment.