Re: [pygccxml-development] Parsing a single header file for the whole project

[Benoît L. <ben...@gm...>]

I've just realized this is the same topic as another thread, which
should help me fix my problem.
Don't know how I could miss it the first time....
So, you can ignore this thread.

Le 1 avril 2010 14:38, Benoît Leveau <ben...@gm...> a écrit :
> Hi all,
>
> There's something that's driving me mad, and I'm sure it's really
> basic or simple to fix.
> I have a big project to bind and parsing all the files takes a lot of
> time, and finally hit the 8GB point at which I prefer to kill the
> process.
> In the "Best practices" page, it is suggested to "Create one header
> file, which will include all project header files.". I've tried that,
> both manually (creating the file on disk and then only parsing this
> file), or automatically (using module_builder.create_text_fc to
> construct a file based on a list of files), and in both ways py++
> doesn't generate any binding.
>
> I mean if I try to parse:
> - A.h and B.h I will get the wrappers for the classes from these files,
> - but if I try with a X.h which contains
> #include "A.h"
> #include "B.h"
> nothing is wrapped by Py++.
>
> I only get these files generated:
> exposed_decl.pypp.txt
> PROJECTNAME.main.cpp (this file is almost empty, ie. it doesn't
> register any class)
> named_tuple.py
>
> Any idea, clue?
>
> Thanks for your help.
>