On Wed, Dec 21, 2011 at 2:44 AM, Davidson, Josh <josh.david...@lmco.com> wrote: > I did run into a couple subtle problems with this approach. Depending on > where I put the header file, Py++ doesn't generate pypp.hpp/pypp.cpp files > that actually register the data structures. Everything shows up in the > exposed_decl.pypp.txt file, but there are no Py++ generated source files to > actually get compiled into the extension. Just where the file can be placed > and where it can't is quite puzzling. Initially, I wanted to build the fake > header as a string using file_configuration_t and CONTENT_TYPE.TEXT as my > files argument to module builder, but that didn't work. I then created a > real fake header in the filesystem, and it initially didn't work either. > After much trial and error, I found that it would work if placed in certain > directories.
This is a long standing issue with Py++. It can't be solved without breaking backward compatibility to the existing code. You will have to use "include/exclude" functionality to select the desired set of to be exported declarations. Roman _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
