Work on LLDB support outside GSoc

Aetf 7437103 at gmail.com
Sat Apr 23 05:23:45 UTC 2016


Hi Rishabh,

I'm not sure about others, but at least my proposal for the LLDB support
was accepted for the GSoC.

It seems to me that you are trying to write the whole plugin from scratch,
while I'm going to work on the existing code base. I'm not sure which one
is better but I think we can work in parallel and discuss all the
designs/implementations about the debugger plugin. I believe we can both
write better code in this way. :)

This is my first time for GSoC, so I don't know if there's any
policy/restrictions about this but I've seen somewhere mentioned that there
can be multiple efforts towards the same project. So this should not be a
problem.

Unfortunately, I have to prepare for my exams for the following week so I
don't have time to look deeper into the code shortly, but anyway here is my
proposal [1], any thoughts, questions, suggestions are more than welcomed.
And it would be really helpful if you can post yours so we can learn from
each other.

[1]: https://github.com/Aetf/GSoC2016Proposals/blob/master/KDevelop-LLDB.md

Cheers,

Aetf
On Fri, Apr 22, 2016, 23:21 RISHABH GUPTA <rishabh9511 at gmail.com> wrote:

> Hi,
> My proposal for LLDB support was not accepted for GSoc project .I want to
> know whether I can still work on it with the guy who has been selected for
> the project?
>
> My plan was to work on the project in any case (i.e outside gsoc or as a
> gsoc) but didn't know there was some other guy applying for the same
> project.
>
> Since I have already done some work on it and know about the project ,It
> would be good If I  could also work on it .
>
> Thank you:)
> Rishabh
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160423/420e4119/attachment.html>


More information about the KDevelop-devel mailing list