Re: [MeeGo-dev] qt-mobility without gyroscope sensor interface
-Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ext Jia-Chi Lai I found qt-mobility src rpm without the gyroscope sensor interface. Does the qt-mobility would provide gyroscope sensor interface?? when?? It will be supported from mobility 1.2 onwards. http://qt.gitorious.org/qt-mobility/qt-mobility/blobs/HEAD/src/sensors/qgyroscope.h -- Alex ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
[MeeGo-dev] [PATCH/meego-rpm-config] BMC#12456: meego-rpm-config doesn't contain armv7hl + armv7nhl + armv7thl + armv7tnhl in rpmrc, causing %{global_cflags} not to be picked up
From 968427eb8c8acd219a51e2cd650fbf17e7d3aeba Mon Sep 17 00:00:00 2001
---
rpmrc |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/rpmrc b/rpmrc
index 21f363c..858862d 100644
--- a/rpmrc
+++ b/rpmrc
@@ -48,6 +48,10 @@ optflags: armv5tejl %{__global_cflags} -march=armv5te
Optflags: armv5tel %{__global_cflags} -fmessage-length=0
-march=armv5te -mlittle-endian
Optflags: armv6l %{__global_cflags} -fmessage-length=0 -march=armv6
-mlittle-endian -mfpu=vfp -mfloat-abi=softfp -D__SOFTFP__
Optflags: armv7l %{__global_cflags} -fmessage-length=0
-march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3
-mfloat-abi=softfp -D__SOFTFP__
+Optflags: armv7hl %{__global_cflags} -fmessage-length=0
-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 -mno-thumb
+Optflags: armv7nhl %{__global_cflags} -fmessage-length=0
-march=armv7-a -mfloat-abi=hard -mfpu=neon -mno-thumb
+Optflags: armv7thl %{__global_cflags} -fmessage-length=0
-march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 -mthumb
+Optflags: armv7tnhl %{__global_cflags} -fmessage-length=0
-march=armv7-a -mfloat-abi=hard -mfpu=neon -mthumb
optflags: atarist %{__global_cflags}
--
1.7.2.3
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Hi gang, This list is kinda of lonely... So I thought I'd bring this thread back up. The wiki (http://wiki.meego.com/In-vehicle/Roadmap) has a number of features listed but not when they are target for. The bug site has these two items listed (using Meego Features-IVI Features -(meego release)1.2): 8704 ACCEPTED [FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI 11456 INDEFINITION [FEA] [MASTER] Provide OKI IVI IOH drivers for Stephenville platforms So the question is, are the two above the extent of the features expected for 1.2? Thanks, Nasa - jukka eklund jukka.ekl...@nokia.com wrote: Or actually new feature requests go to 'unspecified' first and then the product manager decides on the release? Really good points everyone so far, and it seems a lot of confusion comes from the fact using Bugzilla as the featurezilla :) AFAIK there was a plan to have a separate landing page for Features, I think that would go a long way helping this. One thing I am slightly confused.. I've understood MeeGo is about contribution is king ie. whoever is making a new feature (request) will have to have at least an idea on where the actual contribution (code in most cases) is coming from, if not the whole contribution. Isn't that the case? If so, how will potential interested contributors know what are key things missing from eg. a specific release? Jukka -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of ext Arjan van de Ven Sent: 3. tammikuuta 2011 20:33 To: Dave Neary Cc: meego-dev@meego.com; Pienimaki Sami (Nokia-MS/Tampere); Lavonius Ville (Nokia-MS/Helsinki) Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? On 1/3/2011 10:10 AM, Dave Neary wrote: just as a side note... since we're about two or so weeks away from feature freeze for 1.2 it should be assumed that all feature requests that get filed are for 1.3 ( in fact, that should have been the case from the day that 1.2 development started, back in late October) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] Moving sources from .debuginfo to .debugsources RPM package?
2011/1/19 Carsten Munk cars...@maemo.org: Hi, One of the biggest problems about debugging on mobile devices running MeeGo is that our debuginfo packages currently contain the entire source of the software. While this is nice for stepping through source code, it is horrible for simple backtraces that QA can use - as the needed debuginfo are too big for typical SD cards. Qt debuginfo as an example is -huge- to install :) openSUSE is having since 2008 debuginfo packages for the debug symbols and debugsources for the sources of the software in question on top of that, for those that want to step through code to debug deeper. Since this looks like a relatively straightforward patch, as seen at: https://build.opensuse.org/package/view_file?file=debugsource-package.diffpackage=rpmproject=openSUSE%3AFactorysrcmd5=3b22d3db294c852fb824c0b11f49d51b Would it be accepted if I submitted a patch that added this functionality to our rpm (or the 4.9 work that is ongoing)? I personally think this could make our platform development a lot easier. I've implemented/adapted this from the openSUSE patches, patches added at http://bugs.meego.com/show_bug.cgi?id=12724 - one patch for meego-rpm-config, one for rpm. It was tested in devel:hardfp:base and as seen on http://download.meego.com/live/devel:/hardfp:/base/standard/i686/ and no ill effects seen (unless if you apply rpm before meego-rpm-config, as there will be unpackaged files in debuginfo else) BR Carsten Munk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
On Friday, January 21, 2011, Nasa wrote: Hi gang, This list is kinda of lonely... So I thought I'd bring this thread back up. The wiki (http://wiki.meego.com/In-vehicle/Roadmap) has a number of features listed but not when they are target for. The bug site has these two items listed (using Meego Features-IVI Features -(meego release)1.2): So the question is, are the two above the extent of the features expected for 1.2? Thanks, Nasa I added the MeeGo IVI 1.2 planned features to the bottom of the In-vehicle/Roadmap page you referenced. Thanks for the reminder. Remember this is IVI specific and does not cover the other devices. regards Joel Clark MeeGo IVI program manager ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
- Joel Clark joel.cl...@intel.com wrote: On Friday, January 21, 2011, Nasa wrote: Hi gang, This list is kinda of lonely... So I thought I'd bring this thread back up. The wiki (http://wiki.meego.com/In-vehicle/Roadmap) has a number of features listed but not when they are target for. The bug site has these two items listed (using Meego Features-IVI Features -(meego release)1.2): So the question is, are the two above the extent of the features expected for 1.2? Thanks, Nasa I added the MeeGo IVI 1.2 planned features to the bottom of the In-vehicle/Roadmap page you referenced. Thanks for the reminder. Remember this is IVI specific and does not cover the other devices. regards Joel Clark MeeGo IVI program manager Joel, Good Stuff... Thanks Nasa ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
