However when I run the command “python buildroot/share/PlatformIO/scripts/mc-apply.py” with the json file in the Marlin root dir or in /src it says “No marlin_config.json found.” So why cant it find it?
The rather short instructions in ConfigEmbedding would seem to say that it is NOT automatically imported into the build. In fact the mc-apply.py actually goes and modifies the two configuration.h files. This would be good but it doesn’t work.
Can you please explain in detail how to do this? @CRCinAU
I’ve never actually used this functionality before - personally, I just use the custom builder on my site for my own firmware.
A few things I would check though:
Make sure you’re on the bugfix-2.1.x branch; and
Check which directory you have the json file in.
Looking at the code here:
It seems that the marlin_config.json file looked for in the current directory. As such, you probably have to call the script as its full path + filename from the root of the checked out git repo.
It also looks for Marlin/Configuration.h and Marlin/Configuration_adv.h as well, so they’re also relative paths to the root of the git repo.
Sigh more nightmares trying to make this work. As explained Ive tried the json in both the root and /src. It doesn’t find it. I dont know how to specify the parameters so that it does find it or why its not finding it in the two obvious locations.
Remember this is all so folks can use the dailies as a starting point.
Ive tried the custom builder. Its good, but if you haven’t used it before its very difficult to get a good result from a blank start. And this circles me back to how to get the config from the dailies and then tweak what we want - theres apparently no (simple) way to do this? Folks have been asking and asking and all we get are throw away comments about how it might be done.
What we really need @CRCinAU is some documentation explaining exactly how to do this. Or it would be awesome if the custom builder would allow selection of the dailies config as a starting point.
Can you help us understand what it is about the daily configs that makes them so difficult to reuse in anything other than the daily builds? Somewhere there must be either header files, config.ini or marlin_config.json for each daily machine build?
