kcoreaddons doesn't compile standalone ?

Stephen Kelly steveire at gmail.com
Sun May 13 16:39:56 UTC 2012


Alexander Neundorf wrote:

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

Yes. It doesn't look worthwhile at the moment I think.

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

I'm not certain it will all be splitting. Would it make sense for solid to 
be in the same repo as the solid stuff in kde-runtime (I think so). If so, 
then they should maybe be in the same repo.

Thanks,

Steve.




More information about the Kde-frameworks-devel mailing list