c-cpp | some my shared c or c programs

I'm trying to post json data in C++ with the restc-cpp library and I have this error:

I have different vim-scripts for different filetypes

So I try to get started with cmake for some time now. I want to use rpclib from here. So I started a new project with main.cpp and CMakeLists.txt and copied the rpclib as a subdirectory into my project:

My code is exactly the example from rpclib and looks like this:

I am running VSCode from Windows over an SSH connection to a Centos 7 development machine and I get the error "Skipping CppCheck linter because lintOn 1 is not in 2." This was working perfectly and I have no idea what might have changed to provoke the error. I do not get any squiggles denoting issues in the code editor. I have been unable to find any help online.

My settings.json in the project .vscode directory reads:

Is there a way I can force VSCode to preview *.mdx files as markdown just like it does for *.md files? For reference see how Github shows preview of this mdx file

I know there's an extension MDX Preview but that's not working for next.js project. see open issue.

I tried this vscode setting but doesn't work:

I'm using an Arduino Mega to control a CS1237 ADC. I'm sending a signal to the clock pin and after each clock pulse, waiting 1ms and then reading the response, according to the datasheet I found (via https://github.com/SiBangkotan/CS1237-ADC-cpp-library). This seems to be working in some capacity, because when I do Serial.println() for each bit received, and for the resulting dataword, I get a 24 bit dataword that matches the 24 separate bits I got. However, when I take out the extra debugging uses of Serial.println() that print each bit as they are received, I get a different dataword as well. It's 20 bits of all 1's every single time, instead of 24 bits of various 1's and 0s. I cant figure out why this extra debugging output in the serial communication channel should change the dataword that comes into the serial monitor?

Here's my setup and pre-setup code:

I am using non-blocking IO where I simply try to write and read to a serial port. Reading of the serial port works as expected whereas writing doesn't.

This is how I've set up the serial line. As you can see, it is setup to non-blocking and canonical. Maybe some of the flags are redundant, but they are mostly taken from an example here: Serial setup example

~(background) I mostly code C on Linux but i want to have the ability to code C on Windows 10 every now and then, so i searched and found out VSCode will do the work (for the time being). Did some research, figured out some stuff i needed, but i have a problem with makefile.I have been using makefile in a basic level but it worked no problem on Linux, VSCode not at all.

~(problem) So am having the error in the picture and no matter what extension (for VSC) i tried i couldn't figure out how to run makefile and compile my code.

~(conclusion) From what i see, VSC can't find anything associated with the word 'make' wihich means i am missing some files, extensions or something else. I don't think i do something wrong with extensions, they are pretty straight forward on how they work. (i have listed what i tried at the end of the post)

[IMAGE] When i get the error

[What extensions i tried]

Make: https://marketplace.visualstudio.com/items?itemName=technosophos.vscode-make

makefree: https://marketplace.visualstudio.com/items?itemName=pidesh.makefree

C/C++ Makefile Project: https://marketplace.visualstudio.com/items?itemName=adriano-markovic.c-cpp-makefile-project

Makefile Command Runner: https://marketplace.visualstudio.com/items?itemName=madmous.makefile-command-runner

I'm using the following Dockerfile to install grpc on a build image, build a cpp microservice and put that into a runtime container.

https://github.com/npclaudiu/grpc-cpp-docker/blob/master/Dockerfile

But the part that builds grpc/protobuf takes 2hours+ and that is for one service.