Re: [pygccxml-development] Relative path mismatch
Brought to you by:
mbaas,
roman_yakovenko
From: Roman Y. <rom...@gm...> - 2006-09-26 05:04:48
|
On 9/26/06, Kevin Bluck <kev...@gm...> wrote: > > 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. os.path.abspath was just an example, you can replace it with whatever you want. -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |