Re: [pygccxml-development] Re: Suggested debug output

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

Roman Yakovenko wrote:

> On 5/22/06, Allen Bierbaum <al...@vr...> wrote:
>
>> Roman:
>>
>> I just ran into a strange issue where all the generated code has a
>> hard-coded path in my user directory.  It took me a while to track down,
>> but I finally fixed it.  (I just needed another path in my user include
>> directories)
>>
>> But in the process I added print output in a number of places
>> (include_t, include_directories_t) so I could see the process that the
>> headers were going through to get the final name.  I got to thinking
>> about this and I think this would be useful debug output to send to the
>> logger so users can see how the paths are being normalized and get some
>> insight into what they need to change.
>>
>> Could you add some debug loggin to the header normalization process so
>> people can debug similar problems?  (I found it helpful to have the
>> original header name, the final normalized name, and a current list of
>> include directories used to normalize it)
>>
>> Thanks,
>> Allen
>>
>> PS. I would give you my changes, but they are just hacked up print
>> statements and probably nothing close to where you would really want to
>> put this type of output.
>>
>
> I am fine with those changes. Can you send me the code you hacked?
> Thus I will have better idea and understanding, what you did and what 
> help
> you to fix it.
>
I don't have the code anymore, I removed it once I found the bug.  I 
think you could probably just add some output in the normalize_path 
method (I think I remembered the name correctly).

-Allen

> Thanks
>