You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started to add unit tests for ccnl-core and noticed that our current CMakeLists.txt in test does not support various defines we use over the project. As a side effect our unit tests can't reach certain parts, e.g.
So, we can't simply just turn on all defines/use flags we use over the project, but have to have fine-grained control over which tests are compiled with which use flags. Any thoughts about it and how we achieve this best?
P.S.: If necessary, I can come up with an example in our code base. The above snippet is just for the sake of clarity.
P.P.S.: On a side not, I think that this might also increase the complexity of providing gcov/lcov support for ccn-lite. See also #301
The text was updated successfully, but these errors were encountered:
Description
I've started to add unit tests for
ccnl-core
and noticed that our currentCMakeLists.txt
intest
does not support various defines we use over the project. As a side effect our unit tests can't reach certain parts, e.g.So, we can't simply just turn on all defines/use flags we use over the project, but have to have fine-grained control over which tests are compiled with which use flags. Any thoughts about it and how we achieve this best?
P.S.: If necessary, I can come up with an example in our code base. The above snippet is just for the sake of clarity.
P.P.S.: On a side not, I think that this might also increase the complexity of providing gcov/lcov support for ccn-lite. See also #301
The text was updated successfully, but these errors were encountered: