On Tuesday 10 November 2009, Carlo wrote: > On Tue, Nov 10, 2009 at 7:49 PM, Alexander Neundorf wrote: > > On Tuesday 10 November 2009, Carlo wrote: > >> On Tue, Nov 10, 2009 at 7:03 PM, Peter Kümmel wrote: > >> >> Attached my hardcoded solution handling. On problem is that the name > >> >> of the solution, defined by cmake (for instance 'project(Automoc4)') > >> >> must match the internal emerge name > >> >> self.subinfo.options.make.slnBaseName or self.package, maybe someone > >> >> could help me there. > >> > > >> > It is possible to always use the same solution name? > >> > Is this the intention of 'slnBaseName'? > >> > > >> > Peter > >> > _______________________________________________ > >> > Kde-windows mailing list > >> > Kde-windows@kde.org > >> > https://mail.kde.org/mailman/listinfo/kde-windows > >> > >> I don't know about this option, but I wouldn't use the cmake visual > >> studio generator since it breaks at least in kdelibs > > > > What breaks ? > > I'd really like to know, because I can't remember that I heard of that > > before. > > > > Alex > > if I remember correctly the problem is in solid, the backends dir has > no CMakeLists.txt > http://websvn.kde.org/trunk/KDE/kdelibs/solid/solid/backends/ > and cmake complains that it can't find CMakeLists.txt in that dir even > if it's not needed If that was the problem, I fixed it recently: http://websvn.kde.org/?view=revision&revision=1026870 Alex _______________________________________________ Kde-windows mailing list Kde-windows@kde.org https://mail.kde.org/mailman/listinfo/kde-windows