<div dir="ltr"><div>Albert,<br><br></div>I got all of kdesdk subfolders to build standalone using the attached (huge) patch. I want to get someone besides myself to take a look before I commit it though, but here it makes it so kdesdk can be built as one module, and also each subfolder (except docs) can be built by itself. I removed quite a bit from the top level CMakeLists.txt so it's just a bunch of add_subdirectory calls. I also took out pimlibs detection and couldn't find any subdir that needed/used it. That was either in there from something that has since been removed or is an optional dependency for something. If anyone knows which we may need to tweak this before committing.<br>
<br>thanks,<br>Jeremy<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 12, 2012 at 11:44 AM, Albert Astals Cid <span dir="ltr"><<a href="mailto:aacid@kde.org" target="_blank">aacid@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">El Dimarts, 11 de desembre de 2012, a les 18:03:07, Jeremy Whiting va<br>
escriure:<br>
<div class="im">> Hello all,<br>
><br>
> Thanks to some awesome students in Brazil we have most (maybe all) of the<br>
> kdesdk migration rules written. I have done an initial conversion with the<br>
> existing rules last night and pushed to scratch repos on<br>
> <a href="http://quickgit.kde.org/scratch/whiting/(cervisia" target="_blank">http://quickgit.kde.org/scratch/whiting/(cervisia</a>, dolphin-plugins,<br>
> kapptemplate, kcachegrind, kde-dev-scripts, kde-dev-utils, kompare,<br>
> lokalize, okteta, poxml, strigi-analyzers, and umbrello).git If each of<br>
> you that is a maintainer of one of the above projects could please clone<br>
> the repositories, make sure no tags or branches that you expect are missing<br>
> (and no extra branches that don't belong to your project are in there) then<br>
> mark the "Maintainer approved" column on<br>
> <a href="http://community.kde.org/KDESDK/Git_Migration#Migration_Rules" target="_blank">http://community.kde.org/KDESDK/Git_Migration#Migration_Rules</a> I would<br>
> really appreciate it.<br>
><br>
> The umbrello developers and I are hoping we can do the actual conversion<br>
> this weekend before the 4.10 RC 1 tag, but in order for that to happen we<br>
> need these all to be verified and I need to make it so we can release the<br>
> 4.10 tarball from git repos (I've done that before for kde-edu and<br>
> kde-accessibility, but can't recall how that's done, so will figure that<br>
> out in the next few days).<br>
<br>
</div>The projects don't build standalone (at least poxml doesn't).<br>
<br>
I suggest we/you do the same we did with kdegames, that is, make them build<br>
standalone in svn before the split, so the splitted repo can be verified to<br>
build correctly without any "manual" modification.<br>
<br>
Cheers,<br>
Albert<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> thanks,<br>
> Jeremy Whiting<br>
><br>
> P.S. It would have been much nicer if there were a kdesdk mailing list, but<br>
> I guess since the module is a group of such separate utilities one has<br>
> never been created, should we create one?<br>
><br>
> On Mon, Jun 18, 2012 at 11:51 AM, Nick Shaforostoff <<a href="mailto:shafff@ukr.net">shafff@ukr.net</a>> wrote:<br>
> > > > Currently:<br>
> > > > repo name / display name: lokalize / Lokalize<br>
> > > > description: Computer-aided i18n translation<br>
> ><br>
> > just 'Computer-aided translation'<br>
> ><br>
> > > > project manager (user id on <a href="http://projects.kde.org" target="_blank">projects.kde.org</a> needed): ?, ?, ...<br>
> ><br>
> > my id is 'shaforo'<br>
> ><br>
> > > Data needed!<br>
> > ><br>
> > > > layout in kdesdk:<br>
> > > > /<br>
> > > > +- lokalize<br>
> > > > +- strigi-analyzer<br>
> > > ><br>
> > > > +- po<br>
> > > > +- ts<br>
> > > > +- xliff<br>
> > > ><br>
> > > > +- thumbnailers<br>
> > > ><br>
> > > > +- po<br>
> ><br>
> > i don't really care, but personally i'm for this layout, because lokalize<br>
> > depends on analyzers, but not vice-versa.<br>
> > _______________________________________________<br>
> > Kde-scm-interest mailing list<br>
> > <a href="mailto:Kde-scm-interest@kde.org">Kde-scm-interest@kde.org</a><br>
> > <a href="https://mail.kde.org/mailman/listinfo/kde-scm-interest" target="_blank">https://mail.kde.org/mailman/listinfo/kde-scm-interest</a><br>
</div></div></blockquote></div><br></div>