kcoreaddons doesn't compile standalone ?

[Alexander Neundorf]

On Sunday 13 May 2012, Kevin Ottens wrote:
> On Sunday 13 May 2012 12:24:55 Alexander Neundorf wrote:
> > On Sunday 13 May 2012, David Faure wrote:
> > > But one big module with independent subprojects that don't get compiled
> > > out of the box, sounds like a major pain (lots of manual setup, and
> > > manual scripts for building everything after any change).
> > 
> > Yes, that's what I have to do currently to see whether it builds
> > standalone.
> > 
> > If we had only one way to build it, this one way would rarely get broken
> > accidentially.
> > 
> > Maybe kdesrc-build can be extended to handle it ?
> 
> Not sure it's wise to create work on the kdesrc-build people for a
> temporary situation.

An alternative is simply not to try to build tier>1 libs standalone as long as 
they are still together in one repository.

Yury and Stephen are working on making the export-targets in cmake more 
powerful, but I'm not sure this will still be needed once we have split the 
repositories.

> 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.
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).

This is also a reason for my mail about the planned split granularity.

Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20120513/0fde6393/attachment.html>