Regarding this procedure/tip: https://www.letscontrolit.com/forum/vie ... 962#p62962, I've a new problem.
My Micha_he/espeasy-repository is autopull with espeasy original. If I change the 'define_plugin_sets.h' for my own build, this change prevents synchronization from my repository with the espeasy original. If I commit it, my repository has an additional change, because this file isn't ignored.
Is there another, better working tip for 2-3 own builds with minimal difference to predefined ones ?
Maybe someone like Userbuild1-10, based on a predefined set X, with +/- plugin/controller X, with additional config X. This file should be ignore by GIT and now I could compile my Userbuild X after pulled all new commits.
Custom build not optimal
Moderators: grovkillen, Stuntteam, TD-er
Re: Custom build not optimal
You can define your own build in the Custom.h file.
This one will be ignored by Git.
There is a sample version included to get you started.
If there is a file called Custom.h (mind the capital C) in the same folder where the Custom_sample.h file is located, then PlatformIO will use that file when building any PlatformIO environment with "Custom" in the name.
This one will be ignored by Git.
There is a sample version included to get you started.
If there is a file called Custom.h (mind the capital C) in the same folder where the Custom_sample.h file is located, then PlatformIO will use that file when building any PlatformIO environment with "Custom" in the name.
Re: Custom build not optimal
But I can't define three different custom sets! Or is this possible?
And all changes I've done in the custom.h, are applied to all custom builds. Or?
And all changes I've done in the custom.h, are applied to all custom builds. Or?
Re: Custom build not optimal
When working with Arduino IDE, you will need to have a #define USE_CUSTOM_H or -DUSE_CUSTOM_H so the compiler will use the Custom.h file.
You can rename them, temporarily, but you'll have to not add them in your git commit, as they won't be ignored then.
For maximum control I never enable auto-pull, and never use "Add all", or similar options, before committing.
You can rename them, temporarily, but you'll have to not add them in your git commit, as they won't be ignored then.
For maximum control I never enable auto-pull, and never use "Add all", or similar options, before committing.
/Ton (PayPal.me)
Re: Custom build not optimal
Thats all too much for me.
I use:
ESPEasy/mega --(auto-pull with bot)--> Micha_he/mega --(manual pull)--> VSCode with GIT --> lokalFolder/mega
and sometimes back for simple code-pull-request to ESPEasy. Mostly sync your changes
Local VSCode and folder for some (3-4) custom builds.
I use:
ESPEasy/mega --(auto-pull with bot)--> Micha_he/mega --(manual pull)--> VSCode with GIT --> lokalFolder/mega
and sometimes back for simple code-pull-request to ESPEasy. Mostly sync your changes
Local VSCode and folder for some (3-4) custom builds.
Re: Custom build not optimal
Files that only exist in your local folder, and never added to the repository, do not cause conflicts, except when someone would add a file with the same name. For these Custom-XYZ.h files, that chance is really small, so you can just keep them local, and rename (or copy to Custom.h) as desired. Only the Custom builds will use that Custom.h file.
When choosing to have Custom-1.h .. Custom-10.h, you would also need matching Custom-N PIO environments, and that would become very complicated.
You could also add script(s) to easily switch (copy) a Custom-X.h to Custom.h and run the appropriate PIO command for a build, to make life somewhat more automated
When choosing to have Custom-1.h .. Custom-10.h, you would also need matching Custom-N PIO environments, and that would become very complicated.
You could also add script(s) to easily switch (copy) a Custom-X.h to Custom.h and run the appropriate PIO command for a build, to make life somewhat more automated
/Ton (PayPal.me)
Who is online
Users browsing this forum: Bing [Bot] and 33 guests