# comms_champion

**Repository Path**: fishcrane/comms_champion

## Basic Information

- **Project Name**: comms_champion
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: MPL-2.0
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2025-07-31
- **Last Updated**: 2025-07-31

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# IMPORTANT NOTICE
Since release v4.0 this project is deprecated. For convenience it has been split into 
two separate ones:

- [COMMS Library](https://github.com/commschamp/comms)
- [CommsChampion Tools](https://github.com/commschamp/cc_tools_qt)

Please use them instead.

This project is now a simple wrapper arount the ones listed above. It 
still can be used for backward compatibility, but it is not recommended.

----

This project is a core (and a member) of 
[CommsChampion Ecosystem](https://commschamp.github.io),
which comes to help in 
developing binary communication protocols, with main focus on
**embedded systems** with limited resources (including 
bare-metal ones) and choosing **C++(11)** programming language to do so. 

This project has two major parts: [COMMS Library](#comms-library) and 
[CommsChampion Tools](#commschampion-tools). The library's components
can be used to define protocol messages as well as its transport
framing information using mostly declarative statements of classes and types 
definitions. The tools can be used to visualise, analyse, and debug binary 
communication protocols, which were developed using [COMMS Library](#comms-library).

# COMMS Library
**IMPORTANT**: The COMMS library has been relocated to a 
separate [repository](https://github.com/commschamp/comms). Please open
it to read the description.

# CommsChampion Tools
**IMPORTANT**: The tools have been relocated to a 
separate [repository](https://github.com/commschamp/cc_tools_qt). Please open
it to read the description.

# Branching Model
This repository will follow the 
[Successful Git Branching Model](http://nvie.com/posts/a-successful-git-branching-model/).

The **master** branch will always point to the latest release, the
development is performed on **develop** branch. As the result it is safe
to just clone the sources of this repository and use it without
any extra manipulations of looking for the latest stable version among the tags and
checking it out.

# Contact Information
For bug reports, feature requests, or any other question you may open an issue
here in **github** or e-mail me directly to: **arobenko@gmail.com**. I usually
respond within 24 hours.