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
{{ message }}
This repository was archived by the owner on Dec 18, 2024. It is now read-only.
@@ -18,26 +17,78 @@ If you like this work, which is given to you completely free of charge, please c
18
17
-https://github.com/sponsors/royshil
19
18
-https://github.com/sponsors/umireon
20
19
20
+
This work uses the great contributions from [EdgeYOLO-ROS](https://github.com/fateshelled/EdgeYOLO-ROS) and [PINTO-Model-Zoo](https://github.com/PINTO0309/PINTO_model_zoo).
- Make available detection information for other plugins through settings
47
+
- More real-time models choices
48
+
49
+
## Building
50
+
51
+
The plugin was built and tested on Mac OSX (Intel & Apple silicon), Windows and Linux.
52
+
53
+
Start by cloning this repo to a directory of your choice.
54
+
55
+
### Mac OSX
56
+
57
+
Using the CI pipeline scripts, locally you would just call the zsh script. By default this builds a universal binary for both Intel and Apple Silicon. To build for a specific architecture please see `.github/scripts/.build.zsh` for the `-arch` options.
58
+
59
+
```sh
60
+
$ ./.github/scripts/build-macos -c Release
61
+
```
62
+
63
+
#### Install
64
+
The above script should succeed and the plugin files (e.g. `obs-ocr.plugin`) will reside in the `./release/Release` folder off of the root. Copy the `.plugin` file to the OBS directory e.g. `~/Library/Application Support/obs-studio/plugins`.
65
+
66
+
To get `.pkg` installer file, run for example
67
+
```sh
68
+
$ ./.github/scripts/package-macos -c Release
69
+
```
70
+
(Note that maybe the outputs will be in the `Release` folder and not the `install` folder like `pakage-macos` expects, so you will need to rename the folder from `build_x86_64/Release` to `build_x86_64/install`)
71
+
72
+
### Linux (Ubuntu)
73
+
74
+
Use the CI scripts again
75
+
```sh
76
+
$ ./.github/scripts/build-linux.sh
77
+
```
26
78
79
+
Copy the results to the standard OBS folders on Ubuntu
Note: The official [OBS plugins guide](https://obsproject.com/kb/plugins-guide) recommends adding plugins to the `~/.config/obs-studio/plugins` folder.
27
85
86
+
### Windows
28
87
29
-
### GitHub Actions Set Up
88
+
Use the CI scripts again, for example:
30
89
31
-
To use code signing on GitHub Actions, the certificate and associated information need to be set up as _repository secrets_ in the GitHub repository's settings.
90
+
```powershell
91
+
> .github/scripts/Build-Windows.ps1 -Target x64
92
+
```
32
93
33
-
* First, the locally stored developer certificate needs to be exported from the macOS keychain:
34
-
* Using the Keychain app on macOS, export these your certificates (Application and Installer) public _and_ private keys into a single .p12 file **protected with a strong password**
35
-
* Encode the .p12 file into its base64 representation by running `base64 <NAME_OF_YOUR_P12_FILE>`
36
-
* Next, the certificate data and the password used to export it need to be set up as repository secrets:
37
-
*`MACOS_SIGNING_APPLICATION_IDENTITY`: Name of the "Developer ID Application" signing certificate
38
-
*`MACOS_SIGNING_INSTALLER_IDENTITY`: Name of "Developer ID Installer" signing certificate
39
-
*`MACOS_SIGNING_CERT`: The base64 encoded `.p12` file
40
-
*`MACOS_SIGNING_CERT_PASSWORD`: Password used to generate the .p12 certificate
41
-
* To also enable notarization on GitHub Action runners, the following repository secrets are required:
42
-
*`MACOS_NOTARIZATION_USERNAME`: Your Apple Developer account's _Apple ID_
43
-
*`MACOS_NOTARIZATION_PASSWORD`: Your Apple Developer account's _generated app password_
94
+
The build should exist in the `./release` folder off the root. You can manually install the files in the OBS directory.
0 commit comments