**** BEGIN LOGGING AT Tue May 29 03:00:04 2018 May 29 06:12:02 muneeb17: Where are the generated bindings ? https://github.com/MuneebMohammed/PRUSS-Bindings ? May 29 06:17:43 please push generated bindings on a different branch. May 29 06:18:09 hi zeekhuge May 29 06:19:29 muneeb17[m]: do you tend to be around this time too? May 29 09:08:16 zeekhuge: Is there a way that muneeb17 can share with us the bindings without putting them on the repo? May 29 09:11:35 abhishek_: If we want just to "see" it, a terminal share can work maybe. It will be a suboptimal option if we want a greater level of freedom to go over it. A WIP branch is fine I think in that case ? May 29 09:12:12 I see no problem with a temp branch May 29 09:12:33 A GitHub gist maybe? May 29 09:13:02 Is that a single file ? May 29 09:13:56 The bindings would ideally be a whole folder worth I guess May 29 09:14:01 Maybe make a separate repo for the generated bindings? May 29 09:14:35 In general, I dont have a problem in any case, but I want to see the bindings. May 29 09:14:55 I'd like to see them too May 29 09:16:09 Also, I didnt like putting the C++ bindings in `SWIG` folder. May 29 09:16:42 Ah ! this is getting irritating. I will use swig tonight. For sure. May 29 09:17:06 muneeb17: We want to see the bindings. Please find a resonable way to let us look into it. May 29 09:17:25 Try it ASAP and ping us when done. May 29 10:18:09 zeekhuge: abhishek_ : Wormo : The repo for the generated bindings - https://github.com/MuneebMohammed/pru-swig-bindings May 29 10:48:15 Not very helpful, all binary files May 29 10:48:47 abhishek_: swig generates binary modules only, apart from the intermediate wrapper files. May 29 10:59:04 abhishek_: should i include the wrapper files as well? May 29 11:05:20 muneeb17: Yeah, please upload intermediate files too .. lets see if that can be helpful. May 29 11:07:42 Hmm .. so swig gnereates binaries. That means no tweaking of the code .. and solves problem of "Code quality" completely :P May 29 11:09:43 It actually makes more sense. Generating sensible code from one language to other would be lot more difficult than generating binaries that would result in similar behaviour. May 29 11:15:58 zeekhuge: I have uploaded the wrapper files too May 29 11:17:30 The meaningful stuff is there at the end, I think May 29 11:20:57 uhm .. yeah .. basically this means that the documentation need to be super strong. May 29 11:21:22 And .. I am still kind of `ok` with the fact that it generates binaries. May 29 11:21:44 muneeb17: there was some error mentioned in the report ? May 29 11:21:49 I think it was related to `go`? May 29 11:21:53 *`Go`? May 29 11:22:03 right ? May 29 11:22:05 yeah, bad_alloc error May 29 11:22:12 Do you have enough experience in Go ? May 29 11:22:34 No, I have never used it May 29 11:22:40 oh ! well, we have no intermediate `Go` code, so I dont think thats the right question. May 29 11:22:40 until now May 29 11:23:22 I have used it pretty briefly May 29 11:24:11 abhishek_: can you give me some debugging tips May 29 11:24:29 muneeb17: Can you try asking it with `swig` people ? maybe they have a mailing list or IRC channel May 29 11:24:46 also, did you try to google it ? maybe there is an existing bug or something ? May 29 11:25:00 Can you post the detailed error message? I'll only be able to check after 7pm today May 29 11:25:14 I found a similar error for C#, it was a string memory leak May 29 11:25:27 abhishek_: sure May 29 11:40:15 zeekhuge: abhishek_ : So, should i start with the remaining c++ bindings, except DMA? May 29 11:40:31 Did you see the email ? May 29 11:40:55 oh wait, its in the drafts. Will send out in a bit. May 29 11:40:56 zeekhuge: Yeah, is it decided now? **** ENDING LOGGING AT Wed May 30 03:00:02 2018