Open Cyb3rn0id opened 4 years ago
The .mc3 file was omitted because at this point there are modifications in the source code that the MCC libraries wouldn't reflect. ie mcc was a starting point and some libraries here that MCC would regenerate could produce nonfunctional results as regenerated.
When shall we expect a MCC configuration file?
I think it's bad that the mc3 file is not provided. How can customers use this project effectively as a starting point?
Can you please provide it and then document that it should not be used for regeneration of this particular project until you overcome the complexity?
Hi everyone, I dissected the project to create a "clean starting point" from the mcc generated files. the mcc_generated_files goo is a submodule so please if you want to use clone with --recursive. I needed to do this for a project I'm working on... I can't wait.
Later in the next couple days more projects will appear as mini programs for the different peripherals.
Hopefully this helps some of you to overcome this issue until we can reverse engineer this into an mc3 file.
Hi everyone, I dissected the project to create a "clean starting point" from the mcc generated files. the mcc_generated_files goo is a submodule so please if you want to use clone with --recursive. I needed to do this for a project I'm working on... I can't wait.
Later in the next couple days more projects will appear as mini programs for the different peripherals.
Hopefully this helps some of you to overcome this issue until we can reverse engineer this into an mc3 file.
did you generate the mc3 file?
Thanks.
There is no *.mc3 file in the project. This file is required for easy change configurations from MCC, but is not provided within the project