fsfw/fsfw-from-zero
fsfw/fsfw-from-zero
11
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

lower cmake requirement

Browse Source
This commit is contained in:
Robin Müller 2022-10-05 09:57:53 +02:00
parent 09d43cb015
commit 13c776a19e
No known key found for this signature in database
GPG Key ID: 11D4952C8CCEF814
2 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CMakeLists.txt
View File

@ -1,4 +1,4 @@
cmake_minimum_required(VERSION 3.22.0)
cmake_minimum_required(VERSION 3.16.0)
# We can version our project using CMake
project(fsfw-from-zero VERSION 0.1.0)

8
ws-ipc/README.md
View File

@ -1,7 +1,7 @@
# Inter-Process Communication (IPC) with the FSFW
IPC is a necessary tool to let software entities communicate with each other. In general, for
any Software, there are two primary ways for software entities to communicated with each other:
any Software, there are two primary ways for software entities to communicate with each other:
1. Shared Memory. If memory is shared between threads or tasks, memory access needs to be protected
with a lock, also commonly called Mutex.
@ -18,4 +18,8 @@ if you are completely new to concurrency in C++.
1. Create two threads which run some tasks with a period of 50ms using the
[`std::thread`](https://en.cppreference.com/w/cpp/thread/thread) API
2. Introduce a static global `uint32_t` variable called `SHARED_VARIABLE`
2. Introduce a static global `uint32_t` variable called `SHARED_VARIABLE`
3. Increment the variable in both threads, but ensure that the access
is protected by a [`std::mutex`](https://en.cppreference.com/w/cpp/thread/mutex).
You can also use the [`std::lock_guard`](https://en.cppreference.com/w/cpp/thread/lock_guard)
which is a [RAII-style](https://en.cppreference.com/w/cpp/language/raii) helper object.