kcoreaddons doesn't compile standalone ?

[Alexander Neundorf]

On Monday 14 May 2012, Kevin Ottens wrote:
> On Sunday 13 May 2012 14:06:44 Alexander Neundorf wrote:
> > On Sunday 13 May 2012, Kevin Ottens wrote:
> > > The real solution would be to start splitting the repositories, but I'm
> > > concerned it could be too early in the game, there's still quite some
> > > moves going on.
> > 
> > Yes.
> > The "lots of manual setup" David mentions, will be the normal case for
> > 3rd party developers who want to use let's say some tier>1 library.
> > They will have to get and build all the small repositories themselves one
> > by one, without the help of kdesrc-build.
> 
> Why without the help of kdesrc-build?

This is how I integrate 3rd party libraries into our proprietary application 
at work: it uses cmake, and 3rd party BSD- or similar licensed libraries are 
integrated via cmake's external_project() support and built statically.
If I would want to use kitemmodels, I would want to integrate this as another 
external_project() in our build.
I very much would not want to use a tool which grabs stuff from somewhere from 
the network, I want it to use the files I downloaded and had a look at.
I also would not want to integrate a meta-buildsystem like kdesrc-build as an 
external_project() in a cmake based build.

In a previous job, colleagues had the same view: they had to ship something 
where they are responsible for that it works, so they did not want anything 
which updates or downloads from the net.

If our goal is to ship "normal" libraries, we partly go against this if 
another meta-build system is necessary to use them.

> > At least that's my experience, if you want to build some
> > proprietary/independent package, people in general try to avoid extra
> > dependencies (...that's why we integrated automoc into cmake).
> 
> It's tied for a great deal with the tooling. 

No. Not only in Randa I heard from many people that they cannot use (the 
independent package) automoc at their workplace, simply because it is an 
additional dependency.
I don't see why it should be easier to get kdesrc-build accepted as a 
dependency than getting automoc (which consisted of 1 cpp file) accepted as 
dependency.

I really think if we are targetting Qt-only developers, on one hand splitting 
all our libs into separate repositories (to make them easy to use), but then 
assuming those Qt-only developers will use kdesrc-build to build them is 
wrong. This immediately makes them something special again.

Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20120514/1f0e3b27/attachment-0001.html>