Timeline for Options for designing a generic library
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2023 at 21:05 | vote | accept | Patrick Wright | ||
| Sep 13, 2023 at 20:28 | comment | added | Jaredo Mills | In the spirit of implementing and debugging the logging library only once, why not build and package ETL for both the embedded and PC projects, implement the logging library to depend only on ETL, and package it as a separate project, then add it as dependency to both application projects? Does the PC variant of the logging library need STL definitions which are not supported in ETL? The submodule way is helpful if you're planning to continue developing the logging library in parallel with the application library; in that case just make it part of the app. You can spin it off when stable. | |
| Sep 8, 2023 at 17:04 | answer | added | Mathias Mamsch | timeline score: 0 | |
| Sep 8, 2023 at 14:55 | history | asked | Patrick Wright | CC BY-SA 4.0 |