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
Since this repository has become Axis vendor only there is no
longer a need to separate it from the normal source code.
This commit moves the two files into src/ and removes the
meson option 'vendors'.
Co-authored-by: bjornvolcker <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+10-14Lines changed: 10 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,30 +14,26 @@ signed-video-framework
14
14
| | | └── plugin.c
15
15
| | └── unthreaded-signing
16
16
| | └── plugin.c
17
-
| ├── src
18
-
| | ├── includes
19
-
| | | └── public header files
20
-
| | └── source files
21
-
| └── vendors
22
-
| └── axis-communications
23
-
| └── source files
17
+
| └── src
18
+
| ├── includes
19
+
| | └── public header files
20
+
| └── source files
24
21
└── tests
25
22
```
26
23
27
24
The repository is split into a library and tests. The library is further organized in
28
-
[source code](./lib/src/), [plugins](./lib/plugins/) and [vendors](./lib/vendors/). The source code
29
-
includes all necessary source files for both signing and validation, and there is no conceptual
30
-
difference in building the library for signing or for validation.
25
+
[source code](./lib/src/) and [plugins](./lib/plugins/). The source code includes all necessary
26
+
source files for both signing and validation, and there is no conceptual difference in building the
27
+
library for signing or for validation.
31
28
32
29
Signing is commonly device specific with separate calls for, e.g., reading and using private keys.
33
30
Therefore, the framework uses the concept of signing plugins which implements a set of
34
31
[interfaces](./lib/src/includes/signed_video_signing_plugin.h). The framework comes with both a
35
32
threaded and an unthreaded signing plugin.
36
33
37
-
Further, the framework allows for vendor specific metadata. Adding that on the signing side, and
38
-
interpreting it on the validation side is controlled through vendor specific code.
39
-
40
-
For instructions on how to use the APIs to integrate the Signed Video Framework in either a signing or a validation application, see [lib/](./lib/). Example applications are available in the [signed-video-framework-examples](https://github.com/AxisCommunications/signed-video-framework-examples) repository.
34
+
For instructions on how to use the APIs to integrate the Signed Video Framework in either a signing
35
+
or a validation application, see [lib/](./lib/). Example applications are available in the
There are no pre-built releases. The user is encouraged to build the library from a [release tag](https://github.com/AxisCommunications/signed-video-framework/tags).
0 commit comments