HMake VS comms_champion

Fork from here, then first build Example 1 from here as per instructions. Then create build-dir in SFML and run hhelper twice and hbuild once there.

I wanted to include a modules Hello World example in my project https://github.com/HassanSajjad-302/HMake but I could not. I considered 2 options. 1) Using the STL module source, but that was not available. If it had been available, only one line would have been needed. ADD_MODULE_DIR_TO_TARGET(app, "./modules/", ".*");

I am writing a new build system HMake on top of CMake. Basically, HMake is a C++ library that generates a CMakeLists.txt file. There are very important features missing in it currently. Though I believe they can be added. I was able to generate two trivial CMakeLists.txt files which work for my two projects. One example is the following.

I've been developing CommsChampion Ecosystem for about 9 years as my pet project. It's about easy and compile-time configurable implementation of binary communication protocols using C++11 programming language, with main focus on embedded systems (including bare-metal ones).

If this is the case, for the third stage of the application specific protocol handling I recommend CommsChampion Ecosystem.

I suppose if you develop something that is going to be used in a single project / product without much of a customization, then meta-programming is not really justified. The meta-programming is justified in many cases when you implement some kind of a library, which can be used in multiple independent products, and these uses may require some product specific customizations. For example, I'm developing a solution for implementing binary communication protocols for embedded systems in C++, called CommsChampion Ecosystem. The core component of which is the COMMS library. Every single use of this library requires different customization. Every application may require different polymorphic interface to handle its message objects. I use template meta-programming there to define virtual functions only needed by the application and not adding unnecessary ones. I also use template meta programming to allow customization of the storage data structures and may use different, more optimized code for some.

I use commschamp. You describe the protocol in an XML format, it only supports C++ though