Re: [GSOC] Weekly report
Hey! I did take note of some. I think it should not take too much time to document these. I will surely do this after I am done with running my CTF conversion formula on the linux system. Best, Vidushi On Tue, May 22, 2018 at 3:23 PM, Chris Johnswrote: > On 22/5/18 1:48 am, Vidushi Vashishth wrote: > > > > I was facing a lot of problems trying to get everything running on MacOS. > > Babeltrace in particular had a lot of dependencies and it became > exceedingly > > difficult to build it. > > Are you able to document the dependencies you found? A post to this list is > fine. It would be nice to not to have start that work again. > > Chris > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [GSOC] Weekly report
On 22/5/18 1:48 am, Vidushi Vashishth wrote: > > I was facing a lot of problems trying to get everything running on MacOS. > Babeltrace in particular had a lot of dependencies and it became exceedingly > difficult to build it. Are you able to document the dependencies you found? A post to this list is fine. It would be nice to not to have start that work again. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [GSOC] Weekly report
Hey! I was facing a lot of problems trying to get everything running on MacOS. Babeltrace in particular had a lot of dependencies and it became exceedingly difficult to build it. So after Gedare's suggestion during the weekly meeting, I switched to Ubuntu on my old laptop. The process took a lot of time hence I couldn't accomplish all of my tasks. I did however accomplish 1) and some bits of 4). Here is the link of my blog discussing the use cases you asked for: https://vidushivashishth.github.io/Third-post-copy/ . Let me know if you have suggestions about the use cases. I setup everything including ubuntu 16.04 to rtems sparc-erc32 architecture again on the new machine. I have an idea of what needs to be done to setup CTF conversion. I hope to deliver something concrete in another day's time. I hope that's okay. I however, have learnt to build stuff quicker now. On Mon, May 21, 2018 at 4:04 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello Vidushi, > > do you already have something that we can try out? > > - Vidushi Vashishthschrieb: > > Hi! > > > > As asked by my mentor, I am going to post my weekly project target on the > > mailing list every Monday. For this week I have the following planned: > > > > 1) Develop use cases (common development problems catered to, etc) for > the > > rtems tracing support and identify what all needs to be implemented > around > > with it. This would be documented first in my blog then the users manual. > > > > 2) Create a babeltrace conversion formula for CTF conversion. Document it > > with sufficient example test cases. > > > > 3) Fixing the buffering sample test cases which is currently failing a > > rtems-path check on execution. > > > > 4) Gain familiarity with barectf, identify methods of integrating it with > > rtems-tld output and working on array support for barectf. > > > > > > Best, > > Vidushi > > -- > Sebastian Huber, embedded brains GmbH > > Address : Dornierstr. 4, D-82178 Puchheim, Germany > Phone : +49 89 189 47 41-16 > Fax : +49 89 189 47 41-09 > E-Mail : sebastian.huber at embedded-brains.de > PGP : Public key available on request. > > Diese Nachricht ist keine geschftliche Mitteilung im Sinne des EHUG. > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [GSOC] Weekly report
Hello Vidushi, do you already have something that we can try out? - Vidushi Vashishthschrieb: > Hi! > > As asked by my mentor, I am going to post my weekly project target on the > mailing list every Monday. For this week I have the following planned: > > 1) Develop use cases (common development problems catered to, etc) for the > rtems tracing support and identify what all needs to be implemented around > with it. This would be documented first in my blog then the users manual. > > 2) Create a babeltrace conversion formula for CTF conversion. Document it > with sufficient example test cases. > > 3) Fixing the buffering sample test cases which is currently failing a > rtems-path check on execution. > > 4) Gain familiarity with barectf, identify methods of integrating it with > rtems-tld output and working on array support for barectf. > > > Best, > Vidushi -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.huber at embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschftliche Mitteilung im Sinne des EHUG. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [GSOC] Weekly report
Oh okay, will keep that in mind from the next time! On Tue, May 15, 2018 at 6:31 PM, Gedare Bloomwrote: > Minor nit: please put a short description of your project in the title > (e.g., "tracing") just to avoid overly plain and possibly confusing > titles if multiple students start to do this. Thanks for the update! > > On Mon, May 14, 2018 at 9:12 PM, Vidushi Vashishth > wrote: > > Hi! > > > > As asked by my mentor, I am going to post my weekly project target on the > > mailing list every Monday. For this week I have the following planned: > > > > 1) Develop use cases (common development problems catered to, etc) for > the > > rtems tracing support and identify what all needs to be implemented > around > > with it. This would be documented first in my blog then the users manual. > > > > 2) Create a babeltrace conversion formula for CTF conversion. Document it > > with sufficient example test cases. > > > > 3) Fixing the buffering sample test cases which is currently failing a > > rtems-path check on execution. > > > > 4) Gain familiarity with barectf, identify methods of integrating it with > > rtems-tld output and working on array support for barectf. > > > > > > Best, > > Vidushi > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: [GSOC] Weekly report
Minor nit: please put a short description of your project in the title (e.g., "tracing") just to avoid overly plain and possibly confusing titles if multiple students start to do this. Thanks for the update! On Mon, May 14, 2018 at 9:12 PM, Vidushi Vashishthwrote: > Hi! > > As asked by my mentor, I am going to post my weekly project target on the > mailing list every Monday. For this week I have the following planned: > > 1) Develop use cases (common development problems catered to, etc) for the > rtems tracing support and identify what all needs to be implemented around > with it. This would be documented first in my blog then the users manual. > > 2) Create a babeltrace conversion formula for CTF conversion. Document it > with sufficient example test cases. > > 3) Fixing the buffering sample test cases which is currently failing a > rtems-path check on execution. > > 4) Gain familiarity with barectf, identify methods of integrating it with > rtems-tld output and working on array support for barectf. > > > Best, > Vidushi ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[GSOC] Weekly report
Hi! As asked by my mentor, I am going to post my weekly project target on the mailing list every Monday. For this week I have the following planned: 1) Develop use cases (common development problems catered to, etc) for the rtems tracing support and identify what all needs to be implemented around with it. This would be documented first in my blog then the users manual. 2) Create a babeltrace conversion formula for CTF conversion. Document it with sufficient example test cases. 3) Fixing the buffering sample test cases which is currently failing a rtems-path check on execution. 4) Gain familiarity with barectf, identify methods of integrating it with rtems-tld output and working on array support for barectf. Best, Vidushi ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel