Feature #563
Von Maximilian Seesslen vor 4 Monaten aktualisiert
See wiki for descriptions.
Library should work with project-config-header instead of magically perdefines and pre-declared structures.
A pure template-class works better but still the defines...
Biwak and lepto also needs their defines.
Just a config header without using template class does not work. The eeprom config layout is unknown.
Fooling the compiler (using different structures in different compile units) does work but is not good.
* keep it as template.
* make the structs project-wide available like config
* make the structs generic and cast the apllication-spezific part; but things like "operating-hours" have to be configured.
Adhoc disabling features changes EEPROM layout without changing any version.
Template feels most correct. Having struct like config will be the cleanest implementation.
Its only about vagus/kokon. Just inject the eeprom structure.
<pre><code class="shell">
set_source_files_properties(
vagus.cpp
PROPERTIES
COMPILE_FLAGS
"-include foo.hpp"
)
</code></pre>
Library should work with project-config-header instead of magically perdefines and pre-declared structures.
A pure template-class works better but still the defines...
Biwak and lepto also needs their defines.
Just a config header without using template class does not work. The eeprom config layout is unknown.
Fooling the compiler (using different structures in different compile units) does work but is not good.
* keep it as template.
* make the structs project-wide available like config
* make the structs generic and cast the apllication-spezific part; but things like "operating-hours" have to be configured.
Adhoc disabling features changes EEPROM layout without changing any version.
Template feels most correct. Having struct like config will be the cleanest implementation.
Its only about vagus/kokon. Just inject the eeprom structure.
<pre><code class="shell">
set_source_files_properties(
vagus.cpp
PROPERTIES
COMPILE_FLAGS
"-include foo.hpp"
)
</code></pre>