Re: [pygccxml-development] Re: recent changes to pygccxml\pyplusplus

[Allen B. <al...@vr...>]

Matthias Baas wrote:

> Allen Bierbaum wrote:
>
>> Interesting.  I would like to hear more about that.  I was never able 
>> to figure out what ALL_AT_ONCE did let alone get it to work.  I have 
>> been creating my own temporary file in the wrapper generation 
>> script.  Please tell me more. :)
>
>
> The parser() function has an option "compilation_mode" which can be 
> set to pygccxml.parser.COMPILATION_MODE.ALL_AT_ONCE (default is 
> FILE_BY_FILE):
>
> decls = pygccxml.parser.parse(
>    ...<your options here>....,
>    compilation_mode = pygccxml.parser.COMPILATION_MODE.ALL_AT_ONCE
> )
>
> With this option pyplusplus generates a temporary header (it seems 
> this is even done in memory so no temporary file is used, but I 
> haven't inspected the sources that closely, so I could be wrong) and 
> invokes gccxml only once. So it would relieve you from creating the 
> temporary header yourself. The drawback is that this compilation mode 
> totally ignores the cache. :(

Ah. That is probably why I didn't end up using it.  Using temporary 
files for headers with the md5-based cache is really fairly magical in 
some cases. (for example I use this to force template template 
instantiation in the module builder)  :)

-Allen

>
>
> - Matthias -
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
> language
> that extends applications into web and mobile media. Attend the live 
> webcast
> and join the prime developer group breaking into this new coding 
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> pygccxml-development mailing list
> pyg...@li...
> https://lists.sourceforge.net/lists/listinfo/pygccxml-development
>