Alex Robenko

Hi Ahmed, I think the [tutorial17](https://github.com/commschamp/cc_tutorial/tree/master/tutorials/tutorial17) is what you need. Regards, Alex

Unfortunately the CommsChampion Ecosystem is a poor fit for the **bit** based protocols. It was designed to handle **byte** based ones. There is a limited support for bit based fields...

Hi Mathis, I don't exactly understand what you mean by ICD, but I have had a long term plan to implement automatic protocol specification generated out of schema files. Unfortunately...

Hi Mathis, When I introduced the relevant code, the intention was to put the string encoding information (like ascii, utf-8, etc...) into the schema. The libcommsdsl parses and exposes its...

Sorry, I'm reluctant to add something to the code base I'm personally not ready to maintain.

I guess such docker files are something more personal than generic. I don't think they belong to the repository. I can understand submitting docker files as bug reports to reproduce...

While I understand your reasoning and see the appeal, I'm still reluctant to make it a part of this repository. Here is why: - The primary deliverables of the [CommsChampion...

To the best of my very shallow understanding of the docker ecosystem is that you can create a bootable image which you start and get a console within it, or...

For starters I suggest creating two different containers "apps" and "tools". Please use "develop" branch of the [cc.cmake](https://github.com/commschamp/cc.cmake/) project for now. ### Apps Container - Use [config/AllApps.cmake](https://github.com/commschamp/cc.cmake/blob/develop/config/AllApps.cmake) configuration. - It...

Docker as well as AppImage support are implemented for all the CommsChampion Ecosystem applications in the [cc.cmake](https://github.com/commschamp/cc.cmake) project.