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
* Drop canard_dsdl, use Nunavut instead
* Upgrade CI to LLVM 13
* Actualize license headers
* Support redundant transmission queues and use more consistent public field naming
* Ditch the deprecated canardRxAccept(), rename canardRxAccept2()
* Refactor the API to eliminate the need to cast away const qualifiers; fixes#175
* Tighten up memory checking in the test suite -- add canaries
* Fix race condition in the roundtrip test
* Do not use Catch2 macros from non-main thread because it is not thread-safe
* Support CANARD_CONFIG_HEADER
* CI: add style_check job
* Use AVL tree in the transmission queue
* Remove all linked lists
* Reduce indirection, pointer casts, and memory footprint by exposing the AVL tree in the public API
* Disable C++-specific warnings as they make no sense for a C library
* Add table-based CRC option (#186)
* CI: disable SonarCloud on forks
* Add docker utilities (#187)
* Add acceptance filter configuration helpers (#171)
Co-authored-by: Kalyan Sriram <coder.kalyan@gmail.com>
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+10-8
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,6 @@ The code shall follow applicable high-reliability coding guidelines as explained
8
8
The implementation shall be fully compliant with the UAVCAN/CAN specification.
9
9
10
10
The implementation and the API should be kept simple.
11
-
The core library `canard.c` (that is, excluding the optional DSDL presentation layer extension) shall never become
12
-
larger than 1000 logical lines of code.
13
-
This restriction ensures that the library is kept simple and easy to validate and verify.
14
11
There will be no high-level abstractions -- if that is desired, other implementations of UAVCAN should be used.
15
12
16
13
The library is intended for deeply embedded systems where the resources may be scarce.
@@ -53,12 +50,13 @@ to prevent non-compliant code from being accepted into upstream.
53
50
54
51
## Tools
55
52
56
-
The following tools are required to conduct library development locally:
53
+
The following tools are required to conduct library development locally
54
+
(check the CI workflow files for the required versions):
57
55
58
-
- GCC v10 or newer.
59
-
- Clang and Clang-Tools v11 or newer.
60
-
- CMake v3.12 or newer.
61
-
- An AMD64 machine.
56
+
- GCC
57
+
- Clang and Clang-Tools
58
+
- CMake
59
+
- An AMD64 machine
62
60
63
61
### Clang-Tidy
64
62
@@ -102,6 +100,10 @@ We would welcome contributions implementing CI/CD testing against popular embedd
102
100
the ARM Cortex M series and AVR in an emulator.
103
101
As a high-integrity library, the Libcanard test suite should provide full test coverage for all commonly used platforms.
104
102
103
+
**WARNING:**
104
+
[Catch2 is NOT thread-safe!](https://github.com/catchorg/Catch2/blob/1e379de9d7522b294e201700dcbb36d4f8037301/docs/limitations.md#thread-safe-assertions)
105
+
Never use `REQUIRE` etc. anywhere but the main thread.
106
+
105
107
## Releasing
106
108
107
109
Simply create a new release on GitHub: <https://github.com/UAVCAN/libcanard/releases/new>
0 commit comments