The recommended Nana way to strip out its functionality is to define WITHOUT_NANA, then all the macros are defined to expand to nothing. However, the Nana include files still need to be present and included to define the empty macros.
It's fairly simple to break this dependency by only including the headers when WITH_NANA is defined instead. There's no legal/licensing need to do this as the licenses are compatible, nor a supply chain management need because the library is basically finished and has no new commits. But it is slightly cleaner from the modularity point of view.
sasagawa888
commented
1 year ago
The recommended Nana way to strip out its functionality is to define
WITHOUT_NANA, then all the macros are defined to expand to nothing. However, the Nana include files still need to be present and included to define the empty macros.It's fairly simple to break this dependency by only including the headers when
WITH_NANAis defined instead. There's no legal/licensing need to do this as the licenses are compatible, nor a supply chain management need because the library is basically finished and has no new commits. But it is slightly cleaner from the modularity point of view.Suggested in issue #225.