4 Jun
2021
4 Jun
'21
9:16 a.m.
On 6/4/21 5:10 AM, Damian Vicino via Boost wrote:
Is it possible to maybe set a CMakeLists.legacy which is what we distribute right now, and a new CMakeLists.txt requiring 3.10 or something like that. We do not maintain the legacy one and anything new gets to the new one. But we keep it around in case someone wants to still build in an old system. Unless any significant change is done to the source-tree the old one should keep working. Right?
If we don't maintain it then it doesn't work pretty soon. No, I'm opposed to maintaining a *third* build system.