Re[2]: %include

Hello Marcelo,

    but for that case with PartA and PartB it works alright. Thanks.
    

Best regards,
 Kerim                            mailto:warkid@xxxxxxxxx

Friday, November 21, 2003, 12:42:12 AM, you wrote:

MM> I added a patch for the include files with identical base names,
MM> you can try by getting the CVS version, as usual.

MM> Marcelo


MM> Kerim Borchaev wrote:

>>Hello David,
>>
>>Monday, November 17, 2003, 4:15:02 PM, you wrote:
>>
>>DB> Kerim Borchaev writes:
>>DB>  > Hello Marcelo,
>>DB>  > 
>>DB>  > I've built the CVS version and for that example it works. But only if
>>DB>  > working directory is ./module. Otherwise it fails with:
>>DB>  > main.i:2: Unable to find 'PartA/main.i'
>>DB>  > I think it would be consistent if it would work too.
>>DB>  > And when it is implemented you could stop searching files relative to
>>DB>  > the working dir;-)
>>DB>  > 
>>
>>DB> I'm not sure I follow--in fact, I don't follow.  Do you have a
>>DB> specific example?
>>
>>Hm. It seems that I didn't follow;-(
>>
>>
>>1. Am I right that swig caches include files by the name it was used in
>>%include? So that %include with the same param as one othe previously
>>parsed won't do anything?
>>
>>I have this structure(a real example):
>>/module
>>        main.i
>>        /src
>>             main.i
>>             header.i
>>
>>- If working directory is ./module.
>>
>>- If src/main.i has this string:
>>%include subsidiary0.i
>>
>>This code of /module/main.i would compile without an error:
>>%module module
>>%include src/main.i
>>%include header.i
>>
>>So the last line "reuses" subsidiary0.i that was included in
>>PartA/main.i?
>>
>>But including the same file twice is possible:
>>//This code in /module/main.i will include src/header.i twice
>>%module module
>>%include src/main.i
>>%include src/header.i
>>
>>And I've been thinking along the lines that files wouldn't be caches
>>by name used in %include. And searched relative to the file directory
>>it was included in:
>>Having this structure:
>>/..
>>    /PartA
>>        main.i
>>        header.i
>>    /PartB
>>        main.i
>>        header.i
>>
>>Each main.i would include it's own header.i with the same
>>%include header.i
>>
>>2. Something strange happens with path formatting(OS is Windows XP):
>>
>>./
>>        /src
>>             main.i
>>                   %include header.i
>>             header.i
>>
>>This command:
>>swig -python -c++ "src\main.i"
>>fails with "src\main.i:2: Unable to find 'header.i'"
>>
>>But this one:
>>swig -python -c++ "src/main.i"
>>produces src/main_wrap.cxx without a problem.
>>
>>Best regards,
>> Kerim                            mailto:warkid@xxxxxxxxx
>>
>>DB> -- Dave
>>
>>
>>_______________________________________________
>>Swig maillist  -  Swig@xxxxxxxxxxxxxxx
>>http://mailman.cs.uchicago.edu/mailman/listinfo/swig
>>  
>>


_______________________________________________
Swig maillist  -  Swig@xxxxxxxxxxxxxxx
http://mailman.cs.uchicago.edu/mailman/listinfo/swig