On Saturday 21 April 2012, Alexander Neundorf wrote:
> On Saturday 21 April 2012, Stephen Kelly wrote:
...
> > What if I also have KCoreAddons installed in /opt/myotherkf5 ? How would
> > I decide which KF5-cmake-container-prefix to use? Environment variables
> > and wrapper scripts?
>
> As always
On Saturday 21 April 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> >> instead of maintaining a list of 'known' components. This would make the
> >> FindKDEFrameworks some kind of 'reflector' for finding frameworks which
> >> adds consistency of versions etc.
> >
> > I thought about this
Alexander Neundorf wrote:
>> instead of maintaining a list of 'known' components. This would make the
>> FindKDEFrameworks some kind of 'reflector' for finding frameworks which
>> adds consistency of versions etc.
>
> I thought about this.
> IMO it is a good thing to have a hardcoded list of known
Hi,
On Saturday 21 April 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > Hi,
> >
> > so here's my proposal:
> >
> > * we will have a separate KF5 package, which will be a build-time
> > requirement for building KDE frameworks libraries. It will offer the
> > following features
> > **
Alexander Neundorf wrote:
> Hi,
>
> so here's my proposal:
>
> * we will have a separate KF5 package, which will be a build-time
> requirement for building KDE frameworks libraries. It will offer the
> following features
> ** KDE approved compiler settings
> ** KDE conforming install dirs
> **
Hi,
AFAIK there is still one feature missing in cmake which we'd really like to
have.
Currently it is not possible to install multiple target exports from a single
project, potentially with dependencies between each other.
I'd like to concentrate on the buildsystem in KDE in the next weeks.
So
