On Mon, May 14, 2012 at 8:55 PM, Rick Stockton
wrote:
> On Mon, 14 May 2012 13:59:43 +0200, todd rme wrote:
>
>> It sounds like this is being limited to just mouse and keyboard
>> shortcuts. Is there a reason this can't be made more general, so
>> other devices can provide shortcuts as well?
On Monday 14 May 2012 23:11:22 David Faure wrote:
> On Monday 14 May 2012 19:46:29 Kevin Ottens wrote:
> > On Sunday 13 May 2012 21:27:40 David Faure wrote:
> > > On Saturday 12 May 2012 23:24:04 Kevin Ottens wrote:
> > > > Git commit f1eee305fe31b002b8f35738873fe45dedf83fc1 by Kevin Ottens.
> > >
On Monday 14 May 2012 23:32:10 Alexander Neundorf wrote:
> On Monday 14 May 2012, David Faure wrote:
> > On Monday 14 May 2012 23:22:09 Alexander Neundorf wrote:
> > > On Monday 14 May 2012, Alexander Neundorf wrote:
> > > ...
> > >
> > > > For now, you can change the code e.g. to
> > > > if (NOT
On Monday 14 May 2012, David Faure wrote:
> On Monday 14 May 2012 23:22:09 Alexander Neundorf wrote:
> > On Monday 14 May 2012, Alexander Neundorf wrote:
> > ...
> >
> > > For now, you can change the code e.g. to
> > > if (NOT TARGET Qt5::Core)
> > >
> > > message(STATUS "DF: Qt5CoreConfig.cmak
On Monday 14 May 2012, David Faure wrote:
> On Monday 14 May 2012 23:13:44 Alexander Neundorf wrote:
> > if (NOT TARGET Qt5::Core)
> >
> > add_library(Qt5::Core SHARED IMPORTED)
> >
> > endif()
>
> Thanks, that works, and is MUCH simpler too ;-)
>
> Any reason against committing that upstream
On Monday 14 May 2012 23:22:09 Alexander Neundorf wrote:
> On Monday 14 May 2012, Alexander Neundorf wrote:
> ...
>
> > For now, you can change the code e.g. to
> > if (NOT TARGET Qt5::Core)
> >
> > message(STATUS "DF: Qt5CoreConfig.cmake add_library(Qt5::Core)")
> > add_library(Qt5::Core SHA
On Monday 14 May 2012, Alexander Neundorf wrote:
...
> For now, you can change the code e.g. to
> if (NOT TARGET Qt5::Core)
> message(STATUS "DF: Qt5CoreConfig.cmake add_library(Qt5::Core)")
> add_library(Qt5::Core SHARED IMPORTED)
> endif()
>
> OR
>
> if (NOT _qt5CoreTargetExists)
> set(_Q
On Monday 14 May 2012 23:13:44 Alexander Neundorf wrote:
> if (NOT TARGET Qt5::Core)
> add_library(Qt5::Core SHARED IMPORTED)
> endif()
Thanks, that works, and is MUCH simpler too ;-)
Any reason against committing that upstream? Requires a too recent cmake?
--
David Faure, fa...@kde.org, http
On Monday 14 May 2012, Alexander Neundorf wrote:
> On Monday 14 May 2012, David Faure wrote:
> > On Monday 14 May 2012 18:10:19 David Faure wrote:
> > > Hi (Steve),
> > >
> > > It seems that updating Qt5 to the latest master broke my
> > > kdelibs-frameworks-qt5 build?
> > >
> > > CMake Error at
On Monday 14 May 2012 23:05:01 Alexander Neundorf wrote:
> On Monday 14 May 2012, David Faure wrote:
> > On Monday 14 May 2012 18:10:19 David Faure wrote:
> > > Hi (Steve),
> > >
> > > It seems that updating Qt5 to the latest master broke my
> > > kdelibs-frameworks-qt5 build?
> > >
> > > CMake E
On Monday 14 May 2012 19:46:29 Kevin Ottens wrote:
> On Sunday 13 May 2012 21:27:40 David Faure wrote:
> > On Saturday 12 May 2012 23:24:04 Kevin Ottens wrote:
> > > Git commit f1eee305fe31b002b8f35738873fe45dedf83fc1 by Kevin Ottens.
> > > Committed on 12/05/2012 at 23:22.
> > > Pushed by ervin in
On Monday 14 May 2012, David Faure wrote:
> On Monday 14 May 2012 18:10:19 David Faure wrote:
> > Hi (Steve),
> >
> > It seems that updating Qt5 to the latest master broke my
> > kdelibs-frameworks-qt5 build?
> >
> > CMake Error at
> > /d/qt/5/qtbase-master/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:6
On Monday 14 May 2012 18:10:19 David Faure wrote:
> Hi (Steve),
>
> It seems that updating Qt5 to the latest master broke my
> kdelibs-frameworks-qt5 build?
>
> CMake Error at
> /d/qt/5/qtbase-master/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:60
> (add_library): add_library cannot create imported targ
On Monday 14 May 2012 22:36:51 Alexander Neundorf wrote:
> On Monday 14 May 2012, Kevin Ottens wrote:
> > On Monday 14 May 2012 21:22:25 Alexander Neundorf wrote:
> ...
>
> > > If our goal is to ship "normal" libraries, we partly go against this if
> > > another meta-build system is necessary to u
On Monday 14 May 2012 22:25:30 Alexander Neundorf wrote:
> On Monday 14 May 2012, Kevin Ottens wrote:
> > On Monday 14 May 2012 21:43:06 Alexander Neundorf wrote:
> > > On Monday 14 May 2012, Kevin Ottens wrote:
> > > > Right now, by default I'd expect maintainers to also maintain their
> > > > bui
On Monday 14 May 2012, Kevin Ottens wrote:
> On Monday 14 May 2012 21:22:25 Alexander Neundorf wrote:
...
> > If our goal is to ship "normal" libraries, we partly go against this if
> > another meta-build system is necessary to use them.
>
> Note I never said "necessary"... It's not "necessary" to
On Monday 14 May 2012, Kevin Ottens wrote:
> On Monday 14 May 2012 21:43:06 Alexander Neundorf wrote:
> > On Monday 14 May 2012, Kevin Ottens wrote:
> > > Right now, by default I'd expect maintainers to also maintain their
> > > buildsystem. *But*, it'll have to be documented what should be in the
On Monday 14 May 2012 21:22:25 Alexander Neundorf wrote:
> On Monday 14 May 2012, Kevin Ottens wrote:
> > On Sunday 13 May 2012 14:06:44 Alexander Neundorf wrote:
> > > On Sunday 13 May 2012, Kevin Ottens wrote:
> > > > The real solution would be to start splitting the repositories, but
> > > > I'm
On Monday 14 May 2012 21:43:06 Alexander Neundorf wrote:
> On Monday 14 May 2012, Kevin Ottens wrote:
> > Right now, by default I'd expect maintainers to also maintain their
> > buildsystem. *But*, it'll have to be documented what should be in the
> > buildsystem and how. We need a clear reference
On Sunday 13 May 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Sunday 13 May 2012, Stephen Kelly wrote:
> >> Alexander Neundorf wrote:
> > ...
> >
> >> > This means either we need to put a lot of work in the buildsystem, to
> >> > handle all cases correctly (and clean up afterwards
On Monday 14 May 2012, Kevin Ottens wrote:
> On Friday 11 May 2012 22:55:37 Alexander Neundorf wrote:
> > I mean, I'm all for modularisation, making it easier to use parts of
> > kdelibs instead of the whole thing.
> > But is it really necessary to split each tiny lib into their own
> > repository
On Monday 14 May 2012, Kevin Ottens wrote:
> On Sunday 13 May 2012 14:06:44 Alexander Neundorf wrote:
> > On Sunday 13 May 2012, Kevin Ottens wrote:
> > > The real solution would be to start splitting the repositories, but I'm
> > > concerned it could be too early in the game, there's still quite s
On Mon, 14 May 2012 13:59:43 +0200, todd rme wrote:
It sounds like this is being limited to just mouse and keyboard
shortcuts. Is there a reason this can't be made more general, so
other devices can provide shortcuts as well? Currently we have a
variety of devices with their own unique bu
On Sunday 13 May 2012 14:06:44 Alexander Neundorf wrote:
> On Sunday 13 May 2012, Kevin Ottens wrote:
> > The real solution would be to start splitting the repositories, but I'm
> > concerned it could be too early in the game, there's still quite some
> > moves going on.
>
> Yes.
> The "lots of man
On Friday 11 May 2012 22:55:37 Alexander Neundorf wrote:
> I mean, I'm all for modularisation, making it easier to use parts of kdelibs
> instead of the whole thing.
> But is it really necessary to split each tiny lib into their own repository
> ?
Well, obviously I think it is for consistency and
On Sunday 13 May 2012 21:27:40 David Faure wrote:
> On Saturday 12 May 2012 23:24:04 Kevin Ottens wrote:
> > Git commit f1eee305fe31b002b8f35738873fe45dedf83fc1 by Kevin Ottens.
> > Committed on 12/05/2012 at 23:22.
> > Pushed by ervin into branch 'frameworks'.
> >
> > Move kconfig_compiler tests i
Hi (Steve),
It seems that updating Qt5 to the latest master broke my kdelibs-frameworks-qt5
build?
CMake Error at /d/qt/5/qtbase-master/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:60
(add_library):
add_library cannot create imported target "Qt5::Core" because another
target with the same name alr
On Thu, May 10, 2012 at 11:21 PM, Mark wrote:
> Hi,
>
> Making this quite detailed and long mail as per request from David Faure
> (twice) ;)
>
> So, I've been patching KShortcut up to support multiple
> shortcuts: https://git.reviewboard.kde.org/r/104801/ and it's working just
> fine with that pa
Stephen Kelly wrote:
> Or there could be issues in the Qt 5 CMake files which are critical to
> KF5, but which have not been found yet for the same reasons
> (configurations different to what I use). Then they might not be fixed
> until Qt 5.1.
>
> Building against Qt 4 will not expose all the is
29 matches
Mail list logo