Closed wgtdkp closed 5 years ago
makes sense.
How much should the configure.h file be available to an external program? Should we just removed the configure.h file from cose.h?
It seems that there is no necessary to include configure.h
in cose.h
, I will agree on removing it.
There is no necessary for an application to include configure.h
. But, if we move configure.h
to include/
, applications using COSE-C
are suggested to change macros in configure.h
to enable/disable specific algorithms. It could be useful to reduce resources when it is used in embedded systems.
So, my opinion will be:
configure.h
from cose.h
configure.h
could be useful
It is weird that a header file
cose.h
ininclude/
needs to includeconfigure.h
insrc/
. Application using COSE-C should only need to setCOSE-C/include
as header directory, but it currently needs to setCOSE-C/src
also.The interface(
include/
) should not depend on the implementation(src/
).So, I think we should move
configure.h
toinclude/
.