Re: [pygccxml-development] Relative path mismatch

[Kevin B. <kev...@gm...>]

> If you use SVN version, than split_module returns list of generated 
> files and provides you a way to tell what should be done with "no more 
> in use" generated files. By default Py++ will delete them.

User would have to regenerate the build script (makefile, jamfile, whatever) 
every Py++ run to make use of that, though.

> mb = module_builder_t( ... )
> mb.build_code_creator( ... )
> my_dir = os.path.abspath('.') #for example
> mb.code_creator.user_defined_directories.append( my_dir )

Thanks, this strips the leading path cruft from the #include directives, which 
is quite acceptable.

It's not actually necessary to do the os.path.abspath() call. It works with 
the relative paths as well.

Naturally, you have to append *both* the lib include *and* the destination 
source folders to user_defined_directories to get both categories of #include 
directives stripped.

--- Kevin