Allow per-platform keywords.txt #3847
Conversation
|
Would this also fix #2996 ? |
|
Yes, I believe it should partially fix #2996. The keywords are only re-read when changing architecture folders. If you have a AVR board which uses hardware/arduino/avr for its boards.txt and platform.txt and you switch to a different board, keywords will not be re-read if the new board also uses hardware/arduino/avr. But if you switch to a board that uses hardware/HoodLoader2/avr as its boards.txt and platform.txt, then keywords will be re-read. Any chance you could give the arduinobot build a quick try? Would be nice if someone (other than me) could at least confirm it works in at least 1 quick test... |
|
The specific issue I linked is fixed with this. |
|
Good :) Is the assumption correct that keywords only need to be re-read when a board change switches to a new architecture folder? Are there any cases where this would be needed changing between boards that share the same architecture folder? |
|
I think the behavior is correct like this. I havent looked at the patch itself but from the logic you described it is correct, no need for a further change. |
Allow per-platform keywords.txt
|
[LMNTS] |
This patch allows platforms to define an keywords.txt file, to add their unique keywords. When a board change also changes platforms, the keywords are reloaded and all editor windows updates with the new keywords.