and this one:
heena@heena-Aspire-5750:~/plasma-framework/build$ cmake
-DCMAKE_INSTALL_PREFIX=$KF5 -DCMAKE_PREFIX_PATH=$KF5 ..
CMake Error at /home/heena/kf5/share/ECM/find-modules/FindKF5.cmake:124
(message):
KF5: requested unknown components KIO;KUnitConversion;KDE4Attic
Call Stack (most recent
Hi ,
I am getting cmake error when I build plasma-framework
http://pastebin.com/raw.php?i=aHbnWHbn .I have build framework branch of
kdelibs .KIndly suggest something .
Regards
--
-Heena
Season of kde'12 participant
Google Summer of Code 2013
Delhi College of Engineering(COE),India
: kde-frameworks-de...@kde.org
M +6-0CMakeLists.txt
http://commits.kde.org/plasma-framework/39cd64fc68b1dc2fc06f308e73ec5be1c78d28f6
diff --git a/CMakeLists.txt b/CMakeLists.txt
index d4d0a43..4ca55c9 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -40,6 +40,12 @@ endif()
# in the
Hello,
On Monday 01 July 2013 07:05:03 Kevin Ottens wrote:
> On Sunday 30 June 2013 22:48:50 Ivan Čukić wrote:
> > > > +1 ABI should be the same in both versions (unlike gcc's std::list
> > > > iirc)
> > >
> > > Just wondering, was this email as "OK, I see where you come from", or
> > > was
> > >
On Sunday 30 June 2013 22:48:50 Ivan Čukić wrote:
> > > +1 ABI should be the same in both versions (unlike gcc's std::list iirc)
> >
> > Just wondering, was this email as "OK, I see where you come from", or was
> > it
> I think we should discuss this at Akademy (with Aaron, Martin and Marco as a
>
> > +1 ABI should be the same in both versions (unlike gcc's std::list iirc)
>
> Just wondering, was this email as "OK, I see where you come from", or was it
I think we should discuss this at Akademy (with Aaron, Martin and Marco as a
minimal WG).
I'd separate the discussion in three parts tha
(unlike gcc's std::list iirc)
Just wondering, was this email as "OK, I see where you come from", or was it a
"OK, let's deal with the C++11 dependency in plasma-framework the same way
than the rest of KDE Frameworks as lamely described"?
Matters to me because that me
> > I don't agree that these /additional/ features are about the api.
> > is an (IMO) immensely useful, especially with lambdas and
> > std::bind for actual non exposed parts.
>
> Well, yes that's all useful. That's the type of things I'd like to use
> everywhere too. I badly worded that above t
On Friday 28 June 2013 23:58:21 Ivan Čukić wrote:
> > OK, then we got a misunderstanding somewhere...
> >
> > Using those Q_* macros is perfectly fine (and even encouraged, we already
> > use Q_DECL_OVERRIDE and I'd like to see more Q_NULLPTR for instance). They
> > enable exactly what I was descr
> OK, then we got a misunderstanding somewhere...
>
> Using those Q_* macros is perfectly fine (and even encouraged, we already
> use Q_DECL_OVERRIDE and I'd like to see more Q_NULLPTR for instance). They
> enable exactly what I was describing earlier: works without C++11 support,
> you get extra
On Friday 28 June 2013 23:13:34 Ivan Čukić wrote:
> > such a premise VS2012 has a very partial C++11 support, Android NDK uses
> > gcc 4.6 by default (apparently you can upgrade that to 4.7 but we can't
> > expect third parties to do it by default, means partial support in both
> > cases), BB10 cro
> such a premise VS2012 has a very partial C++11 support, Android NDK uses
> gcc 4.6 by default (apparently you can upgrade that to 4.7 but we can't
> expect third parties to do it by default, means partial support in both
> cases), BB10 cross- compiler doesn't properly support C++11. We're not
T
On Friday 28 June 2013 20:52:59 Aaron J. Seigo wrote:
> On Friday, June 28, 2013 13:08:49 Kevin Ottens wrote:
> > Just to clarify: It's not a "no-no" to using C++11, it's to make sure
> > we're able to build without them.
>
> We have no interest in trying to maintain a build that does not require
On Fri, Jun 28, 2013 at 2:52 PM, Aaron J. Seigo wrote:
> On Friday, June 28, 2013 13:08:49 Kevin Ottens wrote:
>> Just to clarify: It's not a "no-no" to using C++11, it's to make sure we're
>> able to build without them.
>
> We have no interest in trying to maintain a build that does not require C
On Friday, June 28, 2013 13:08:49 Kevin Ottens wrote:
> Just to clarify: It's not a "no-no" to using C++11, it's to make sure we're
> able to build without them.
We have no interest in trying to maintain a build that does not require C++11.
There are too many useful features that we can take adva
> > Isn't the point of a dependency (on C++11) to make it required?
>
> Well, we have required and optional dependencies. C++11 is not special in
> that regard, we can make it either required or optional.
So, essentially, the issue is that Plasma keeps both the framework and the
shells in the s
On Friday 28 June 2013 07:33:43 Shaun Reich wrote:
> On Fri, Jun 28, 2013 at 7:08 AM, Kevin Ottens wrote:
> > On Friday 28 June 2013 11:02:25 Ivan Čukić wrote:
> >> On Friday 28 June 2013 08:13:32 Kevin Ottens wrote:
> >> > Git commit 597397b41f5450f24ddc784e0faa13133fed6bd5 by Kevin Ottens.
> >>
On Fri, Jun 28, 2013 at 7:08 AM, Kevin Ottens wrote:
> On Friday 28 June 2013 11:02:25 Ivan Čukić wrote:
>> On Friday 28 June 2013 08:13:32 Kevin Ottens wrote:
>> > Git commit 597397b41f5450f24ddc784e0faa13133fed6bd5 by Kevin Ottens.
>> > Committed on 28/06/2013 at 08:07.
>> > Pushed by ervin into
On Friday 28 June 2013 11:02:25 Ivan Čukić wrote:
> On Friday 28 June 2013 08:13:32 Kevin Ottens wrote:
> > Git commit 597397b41f5450f24ddc784e0faa13133fed6bd5 by Kevin Ottens.
> > Committed on 28/06/2013 at 08:07.
> > Pushed by ervin into branch 'master'.
> >
> > Revert "Enabling C++11 flags for
On Friday 28 June 2013 08:13:32 Kevin Ottens wrote:
> Git commit 597397b41f5450f24ddc784e0faa13133fed6bd5 by Kevin Ottens.
> Committed on 28/06/2013 at 08:07.
> Pushed by ervin into branch 'master'.
>
> Revert "Enabling C++11 flags for clang and gcc"
This request [1] got a green light by Aaron [2
n optional argument to also specify the type, so from now on installed
service files will not all be plasma-applet-.desktop, but
for example plasma-wallpaper-.desktop.
CCMAIL:plasma-devel@kde.org
M +6-2CMakeLists.txt
http://commits.kde.org/plasma-framework/b679eb6dabea787f4e73097cb340c35b9862
pes/plasma-lookandfeel.desktop
A +6-0src/plasma/data/servicetypes/plasma-shell.desktop
A +5-0src/plasma/data/servicetypes/plasma-wallpaper.desktop
http://commits.kde.org/plasma-framework/53a70b703ddbd940ca5c8d2b27cd15d53f440ad7
diff --git a/src/plasma/data/servicetypes/plasma-lookandfeel.desk
kde.org
M +4-4src/shell/CMakeLists.txt
http://commits.kde.org/plasma-framework/ea41410004e9e634e40124b5d4ac690cecb7b99b
diff --git a/src/shell/CMakeLists.txt b/src/shell/CMakeLists.txt
index 559f927..afa3687 100644
--- a/src/shell/CMakeLists.txt
+++ b/src/shell/CMakeLists.txt
@@
compatible, you'll need to
update your kdelibs[frameworks] to at least 4502362ad.
CCMAIL:plasma-devel@kde.org
M +2-1src/plasma/private/runnerjobs_p.h
http://commits.kde.org/plasma-framework/2c226f6023483f110ac85fbd07528e36675eaf0b
diff --git a/src/plasma/private/runnerjobs_p.
601 - 624 of 624 matches
Mail list logo
