Our great sponsors
-
arm-gtest
This repository contains a sample project for TDD development on ARM devices using Google Test
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
areg-sdk
AREG is an asynchronous Object RPC framework to simplify multitasking programming by blurring borders between processes and treating remote objects as if they coexist in the same thread.
I guess your questionmarks are about installing "bear", he refers to this project: https://github.com/rizsotto/Bear
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.
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.