On Monday 06 June 2011, Brad King wrote:
> On 06/04/2011 06:39 AM, Alexander Neundorf wrote:
> > So, what we came up with is that create a new package which just contains
> > our cmake modules, so they can be used by non-KDE applications.
>
> [snip]
>
> > Do you think this is a reasonable plan or
On 06/04/2011 06:39 AM, Alexander Neundorf wrote:
> So, what we came up with is that create a new package which just contains our
> cmake modules, so they can be used by non-KDE applications.
[snip]
> Do you think this is a reasonable plan or do you see conceptual issues with
> it
This is a gre
On Sunday, June 05, 2011 11:34:55 PM Eric Noulard wrote:
> 2011/6/4 Alexander Neundorf :
> > Hi,
> >
> > again from the KDE sprint...
> >
> > We have around 150 cmake modules in kdelibs...
> > Several libraries are not "before" kdelibs, so they don't have access to
> > those.
> >
> > So, what we
2011/6/4 Alexander Neundorf :
> Hi,
>
> again from the KDE sprint...
>
> We have around 150 cmake modules in kdelibs...
> Several libraries are not "before" kdelibs, so they don't have access to
> those.
>
> So, what we came up with is that create a new package which just contains our
> cmake modul
Hi,
Sounds reasonable to me. It reminds me th autoconf archive project.
Also, I have always been doing the same: keep my cmake modules in a
separate repository which is added as a submodule in all my others
projects.
-Nico
On Saturday, June 4, 2011, Alexander Neundorf wrote:
> Hi,
>
> again fro
Hi,
again from the KDE sprint...
We have around 150 cmake modules in kdelibs...
Several libraries are not "before" kdelibs, so they don't have access to
those.
So, what we came up with is that create a new package which just contains our
cmake modules, so they can be used by non-KDE applicatio
