CMake TCP/UDP/Serial Communication Code Fix for console with protobuf and GTest -- 3
Budget: $30 – $250 USD
I need a TCP/UDP/Serial communication code written in C/C++ for console. The code is very simple and mainly focuses on reconnecting when the connection is lost. Also, I want to build it after compiling protobuf(.proto) file through CMake and finally run google test.
Main requirements:
- Modify existing code based on TCP/UDP/Serial communication. You can replace everything. Currently, only TCP and UDP are written a little. If you open two programs and run them, UDP does not work properly. And please add Serial communication.
- When creating all objects, you must use Smart Pointer safely. You will get a feel for it when you look at the code.
- Basically, the code is written. You can look at the code and modify and add it. It is simple, so you will understand it right away.
- The important thing is that when the other party (B) disconnects (termines the program), A checks the reason why B disconnected, decides whether A will reconnect (when it is a client) or wait for B to connect (when it is a server), and reconnect. You will get a feel for it when you look at the code.
- When building with CMake, it does not work after compiling the protobuf (.proto) file and building. Please resolve this in CMakeList.txt. It seems to be a dependency issue.
- When building with CMake, you should also run Google Test after the build is finished. Please write everything in CMakeList.txt.
Required Skills:
- Strong expertise in C/C++ programming.
- Extensive experience with TCP/UDP/Serial communications.
- Experience with CMake protobuf, google test
Main requirements:
- Modify existing code based on TCP/UDP/Serial communication. You can replace everything. Currently, only TCP and UDP are written a little. If you open two programs and run them, UDP does not work properly. And please add Serial communication.
- When creating all objects, you must use Smart Pointer safely. You will get a feel for it when you look at the code.
- Basically, the code is written. You can look at the code and modify and add it. It is simple, so you will understand it right away.
- The important thing is that when the other party (B) disconnects (termines the program), A checks the reason why B disconnected, decides whether A will reconnect (when it is a client) or wait for B to connect (when it is a server), and reconnect. You will get a feel for it when you look at the code.
- When building with CMake, it does not work after compiling the protobuf (.proto) file and building. Please resolve this in CMakeList.txt. It seems to be a dependency issue.
- When building with CMake, you should also run Google Test after the build is finished. Please write everything in CMakeList.txt.
Required Skills:
- Strong expertise in C/C++ programming.
- Extensive experience with TCP/UDP/Serial communications.
- Experience with CMake protobuf, google test