[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-community
Subject: Re: [kde-community] Proper KDE SDK - was - Re: Applications in KDE Generation 5
From: Pau Garcia i Quiles <pgquiles () elpauer ! org>
Date: 2014-01-16 11:11:31
Message-ID: CAKcBokuh6aCGOPvHd8Hc6u5Lb_hqK3zGOn2x=M5w52dW5j8XBg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello,
Where can I find the CI scripts? If someone could give me access to Jenkins
and give me a little introduction to what's already in place for CI, I can
probably help with automating the SDK generation so that it's available
from the Qt SDK Maintenance Tool.
I am attending FOSDEM, in case you think it's easier to explain in person.
On Thu, Jan 16, 2014 at 9:43 AM, Ben Cooksley <bcooksley@kde.org> wrote:
> On Thu, Jan 16, 2014 at 11:09 AM, Pau Garcia i Quiles
> <pgquiles@elpauer.org> wrote:
> >
> >
> >
> > On Wed, Jan 15, 2014 at 11:00 PM, Albert Astals Cid <aacid@kde.org>
> wrote:
> >
> >>
> >> > * Can we create a "proper" KDE SDK? We have the SDK module which is
> >> > really a mix of general development related apps and KDE-specific dev
> >> > tools, and we have Examples, and we have a few other bits-and-pieces
> >> > scattered around. Can we split the apps off to stand on their own
> >> > repos in Extragear, and merge Examples and the other tools into SDK?
> >>
> >> We can, it just needs manpower ;-)
> >
> >
> > I think I have been asking for a KDE SDK for the last 7 years :-)
> >
> > KF5 should make that easier, given that there are many "small" parts.
> >
> > Another idea: let's make the different parts of the SDK (Tier 1
> components,
> > Tier 2 components, etc) available from a repository that could be
> integrated
> > in the Qt SDK Maintenance Tool.
> >
> > This task is very time consuming (lots of rebuilds and tests) but it
> > shouldn't be too difficult from a technical point of view. It essentially
> > requires CMake knowledge. Jenkins knowledge and access to a powerful
> build
> > machine would be a plus. It's a pity GSoC is so far yet :-/
>
> I'd suggest this get integrated into our existing CI scripts to make
> it easier to perform when needed - they already have 99% of the
> structure and other necessary capability to build all of the
> frameworks. I'd advise against doing this as part of a GSoC project
> however - other than producing the necessary metadata to make the
> "repository" there wouldn't be too much to actually code...
>
> The repository in question can probably be distributed via files.kde.org.
>
> >
> >
> > --
> > Pau Garcia i Quiles
> > http://www.elpauer.org
> > (Due to my workload, I may need 10 days to answer)
>
> Thanks,
> Ben Cooksley
>
> >
> > _______________________________________________
> > kde-community mailing list
> > kde-community@kde.org
> > https://mail.kde.org/mailman/listinfo/kde-community
> _______________________________________________
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listinfo/kde-community
>
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
[Attachment #5 (text/html)]
<div dir="ltr">Hello,<div><br></div><div>Where can I find the CI scripts? If someone \
could give me access to Jenkins and give me a little introduction to what's \
already in place for CI, I can probably help with automating the SDK generation so \
that it's available from the Qt SDK Maintenance Tool.</div>
<div><br></div><div>I am attending FOSDEM, in case you think it's easier to \
explain in person.</div><div><br></div></div><div class="gmail_extra"><br><br><div \
class="gmail_quote">On Thu, Jan 16, 2014 at 9:43 AM, Ben Cooksley <span \
dir="ltr"><<a href="mailto:bcooksley@kde.org" \
target="_blank">bcooksley@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Thu, Jan 16, 2014 at \
11:09 AM, Pau Garcia i Quiles<br> <<a \
href="mailto:pgquiles@elpauer.org">pgquiles@elpauer.org</a>> wrote:<br> ><br>
><br>
><br>
> On Wed, Jan 15, 2014 at 11:00 PM, Albert Astals Cid <<a \
href="mailto:aacid@kde.org">aacid@kde.org</a>> wrote:<br> ><br>
>><br>
>> > * Can we create a "proper" KDE SDK? We have the SDK module \
which is<br> >> > really a mix of general development related apps and \
KDE-specific dev<br> >> > tools, and we have Examples, and we have a few \
other bits-and-pieces<br> >> > scattered around. Can we split the apps off \
to stand on their own<br> >> > repos in Extragear, and merge Examples and \
the other tools into SDK?<br> >><br>
>> We can, it just needs manpower ;-)<br>
><br>
><br>
> I think I have been asking for a KDE SDK for the last 7 years :-)<br>
><br>
> KF5 should make that easier, given that there are many "small" \
parts.<br> ><br>
> Another idea: let's make the different parts of the SDK (Tier 1 \
components,<br> > Tier 2 components, etc) available from a repository that could \
be integrated<br> > in the Qt SDK Maintenance Tool.<br>
><br>
> This task is very time consuming (lots of rebuilds and tests) but it<br>
> shouldn't be too difficult from a technical point of view. It \
essentially<br> > requires CMake knowledge. Jenkins knowledge and access to a \
powerful build<br> > machine would be a plus. It's a pity GSoC is so far yet \
:-/<br> <br>
</div></div>I'd suggest this get integrated into our existing CI scripts to \
make<br> it easier to perform when needed - they already have 99% of the<br>
structure and other necessary capability to build all of the<br>
frameworks. I'd advise against doing this as part of a GSoC project<br>
however - other than producing the necessary metadata to make the<br>
"repository" there wouldn't be too much to actually code...<br>
<br>
The repository in question can probably be distributed via <a \
href="http://files.kde.org" target="_blank">files.kde.org</a>.<br> <div \
class="im"><br> ><br>
><br>
> --<br>
> Pau Garcia i Quiles<br>
> <a href="http://www.elpauer.org" target="_blank">http://www.elpauer.org</a><br>
> (Due to my workload, I may need 10 days to answer)<br>
<br>
</div>Thanks,<br>
Ben Cooksley<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> _______________________________________________<br>
> kde-community mailing list<br>
> <a href="mailto:kde-community@kde.org">kde-community@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/kde-community" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a><br> \
_______________________________________________<br> kde-community mailing list<br>
<a href="mailto:kde-community@kde.org">kde-community@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-community" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-community</a><br> \
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Pau Garcia i \
Quiles<br><a href="http://www.elpauer.org">http://www.elpauer.org</a><br>(Due to my \
workload, I may need 10 days to answer) </div>
_______________________________________________
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic