areg-sdk VS arm-gtest

FP Libraries: gRPC, ZeroMQ, and AREG are examples of libraries with a special focus on providing possibilities for Interprocess Communication. Developed using C++, they facilitate communication through predefined APIs, emphasizing functional programming concepts.

In addition, if the owners of the repositories add more relevant and precise labels to the issues, it increases the possibility that the OSS developers find the issues they would loved to resolve. For example, the issues of AREG SDK which marked "help wanted" in addition have such labels like "C++" or "cmake", "unit test", etc.

My closer introduction with these 2 tools started from OSS areg sdk project. Because of some experienced friend recommendation, i started with make. The main reason was that it is more spread in embedded. No other weighty argument they had. After having make, i decided to integrate cmake. Suddenly i figured out that cmake for me is more understandable and powerful. It already has many features that makes things easier. The biggest advantage for me is that in comparison to make / Makefile, lot of IDE support build with cmake. The cross-platform / cross-compile for areg-sdk is important feature, and this is easier to achieve with cmake. For example, I can compile with make under Linux with gcc/clang, but under windows can compile in cygwin environment and not with MSVC, which is not the issue in case of cmake.

Project: AREG is a cross-platform interface-centric lightweight communication engine, which forms a grid of services in the IoT fog- and mist-network, automates the real-time transmission of data between multiple connected software nodes, so that the connected Things interact like a thin distributed servers and clients. Technologies: C/C++17, standard library dependencies, POSIX and Win32 API. Can be used in real product.

Nice. I also have own project, but it already requires much time, so that cannot join in other projects. As well, up to now have no dependencies, except standard system libraries. I think, we should have a separate post to share projects and give short description. Some might be interested to join.

Here I've crated a list of API that use in the project. Some of methods are part of ncurses.h. So I have a questions:

The learning curve is really not as steep as it may seem. Using Cmake actually makes the whole build process a lot easier and much more modular allowing you to easily swap in/out different components by including different cmake files or not. I made an example repo not so long ago that demonstrates this: link.

A few days ago I posted my sample project which uses the cmake approach for this. As u\embeddedartistry mentioned two output directories are configured, one for native compilation (unit test) and one for cross-compilation (target binaries etc.). I just created a small script that builds both targets with a single command and I find it very pleasant to work with so far. All with a single command you can: build unit tests, run the unit tests, build target binaries and flash binaries onto the target. You can also only run the tests or only flash of course. Essentially it contains different cmake files for each target which are included in the main cmake file so it's easy to swap in/out different libraries or targets.

https://github.com/tomasvr/arm-gtest Hey everyone, a while back I started learning about TDD and how it can be applied to embedded projects (book). I created a sample project which sets up the necessary environment and automates most of the boring stuff so that you can run unit tests natively and flash the target hardware with a single command. By default, the repository is configured for the stm32f1 (blackpill) MCU but it can be configured for other ARM-based MCU supported by libopencm3 as described in the readme. I hope it can be of use to someone!