GSoC 2016 proposal - Kit Selection & Improvements

[Tomaz Canabrava]

Answering on top of things because I'm on the phone.

The main idea is cmake, qmake if time fits (we have a lot of good projects
right now that uses qmake and I actually work in one of those, so I need it
for my work)

And as far as compilation goes, the plan is that only one of the binaries
will be compiled at the time.
Em 28 de mar de 2016 20:11, "Aleix Pol" <aleixpol at kde.org> escreveu:
>
> On Fri, Mar 25, 2016 at 3:57 PM, Tomaz Canabrava <tcanabrava at kde.org>
wrote:
> > Hello,
> >
> > As discussed with Kevin Funk on the past few days, I wanna try to do the
> > GSoC this year on kdevelop - I already have a few patches on it, not
many,
> > and gsoc would help me to actually have a better knowledge and
understanding
> > of internals on KDevelop. :)
> >
> >
> >
https://docs.google.com/document/d/13KJKBfIjf3l1uv6K85UME5LN_WJrx27DJA26nZ9Oqpk/edit?usp=sharing
> >
> > I'll send this as soon as any of you kdevelop guys answers this with a
bit
> > of modifications, since the due-time is today in a few hours.
>
> Hi Tomaz,
> I like your proposal, I would still like to know though how do you
> suggest this to work at a technical level.
> - are you sure it makes sense to abstract it out? Maybe it would be as
> good if it was just implemented for cmake. Coming up with an
> abstraction is a bunch of additional work.
> - I'm guessing that for cmake you plan to get each build in a separate
> build directory. Do you plan to build them always? Or be able to
> select which is the "current" platform? Or do it always knowing that
> it will be usually just the one platform?
>
> Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20160329/fb1e1c77/attachment.html>