diff options
| -rw-r--r-- | README.md | 4 | ||||
| -rw-r--r-- | wrappers/csharp/README.md | 5 | ||||
| -rw-r--r-- | wrappers/python/README.md | 9 |
3 files changed, 10 insertions, 8 deletions
@@ -14,13 +14,11 @@ be downloaded by the caller. ## Build & test Build shared library for current platform: - ```shell make ``` Build shared library for specified OS & architecture (example): - ```shell make OS=windows ARCH=386 ``` @@ -28,13 +26,11 @@ make OS=windows ARCH=386 Results will be output in `exports/`. Test Go code: - ```shell make test-go ``` Test wrappers: - ```shell make test-wrappers ``` diff --git a/wrappers/csharp/README.md b/wrappers/csharp/README.md index a00922a..4b045ac 100644 --- a/wrappers/csharp/README.md +++ b/wrappers/csharp/README.md @@ -1,24 +1,21 @@ First build the shared Go library. Next: Build `EduVpnCommon`: - ```shell make ``` Build as nupkg, including eduvpn_verify library: - ```shell make pack ``` Currently, directly referencing the project may not work if you have multiple dynamic libraries compiled in the `exports` folder. If you instead add the `.nupkg`, e.g. with one of the -methods [here](https://stackoverflow.com/q/43400069) or [here](https://stackoverflow.com/q/10240029) it automatically +methods [here](https://stackoverflow.com/q/43400069) or [here](https://stackoverflow.com/q/10240029), it automatically copies the correct library. Test: - ```shell make test ``` diff --git a/wrappers/python/README.md b/wrappers/python/README.md new file mode 100644 index 0000000..f10e5ad --- /dev/null +++ b/wrappers/python/README.md @@ -0,0 +1,9 @@ +First build the shared Go library. Next: + +No dependencies, just reference `discovery.py` and call `verify`. + +Test: + +```shell +make test +``` |