test: Should add unittests directly on source, don't require compilation / generation from CMake
As I'm exploring the code, I would like to get a better feel for pygccxml
structures, and how that can be used for enumeration to augment the explicit declaration_t
(type x name) enumeration in config files.
At present (a87a911e) the current unittests are more of integration tests - using CMake, generate bindings, compile the bindings, and then test the resulting interfaces in Python. It would be nice to (programmatically and manually) inspect / debug the intermediate results as well.
(I think this may be related to #51)
\cc @joe-snyder
Edited by Eric Cousineau