Just git clone and run ./uc3, see what happens :) changes will happen in autoconfig.h code should be written in config.uc3 It generates C macros based on user input. It prompts for config information based on a written file. The compiler can compile any type of file, though the one shown in the repo is config.uc3. It takes the code from that file (a custom language I made), and defines code, config options, and relationships between the two. I made this in about three weeks and 100 hours. I based it off KConfig, and made it because I needed a powerful configuration system. It also has built in arithmetic and dependency checking.
Just git clone and run ./uc3, see what happens :) changes will happen in autoconfig.h code should be written in config.uc3 It generates C macros based on user input. It prompts for config information based on a written file. The compiler can compile any type of file, though the one shown in the repo is config.uc3. It takes the code from that file (a custom language I made), and defines code, config options, and relationships between the two. I made this in about three weeks and 100 hours. I based it off KConfig, and made it because I needed a powerful configuration system. It also has built in arithmetic and dependency checking.