Christoph Egger writes: > > There are two solutions: > > a) Write a README file, saying to build libgii before
This will not do, because the config.h will not be looked for in the libgii build tree. I could simply put an empty config.h file in the python extension build tree but it's obviously braindead. > b) Rewrite the Python wrapper, so that it doesn't require any config.h file I'd love to, but I need gii internal headers... The real problem is that installed headers should _never_ include a file that is outside of the include tree. I propose moving '#include "config.h"' to .c source files directly. Eric. --
