Meego Wiki
Views

SDK/Documentation/MeetingMinutes/20110112

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Features)
(Features)
Line 74: Line 74:
{{#bugzilla:
{{#bugzilla:
   |columns=id,status,to,severity,version,summary
   |columns=id,status,to,severity,version,summary
-
   |component=Documentation
+
   |component=Tools
   |product=MeeGo SDK features
   |product=MeeGo SDK features
   |status=NEW,NEEDINFO,ASSIGNED,REOPENED
   |status=NEW,NEEDINFO,ASSIGNED,REOPENED

Revision as of 11:30, 12 January 2011

Contents

Attendees

Agenda

  • Documentation-related features listed in Bugzilla for MeeGo 1.2 SDK release.
  • Getting help from the MeeGo Community on documentation related issues: OBS instructions, sample applications -> how to get this started?
  • Architecture documentation status (publishing of docs?)
  • Assigining responsibilities on SDK content areas

Content areas (according to features in Bugzilla)

Question: are we talking about updates, or are these new docs people are requesting? Many of these areas are covered in the SDK docs for 1.1; API refs are on apidocs.meego.com; some docs are elsewhere in the wiki but could be brought into the MeeGo SDK 1.2 TOC. It may be worth discriminating three cases by adding more comments to the bugs: (1) new content; (2) updates to existing content; (3) migration of content to the Developer Guide. -- Elliot Smith 11:20, 12 January 2011 (UTC)

Below listing has been taken from MeeGo 1.2 developer documentation related features in Bugzilla:

  • 9479 Developer documentation: Appropriate documentation shall be provided to developers
    • Responsibility for this area:
  • 9480 Getting started with MeeGo application development: Introductory document for getting started with development.
    • Responsibility for this area:
  • 9481 Installation instructions (OBS): How to install an OBS server & client.
    • Responsibility for this area: OBS server is probably out of scope (but covered by OBS setup anyway); client docs exist already (incomplete) - Build Infrastructure -- Elliot Smith 11:14, 12 January 2011 (UTC)
  • 9482 Installation instructions (application SDK): How to install the application SDK.
    • Responsibility for this area:
  • 9483 Device provisioning instructions: How to take a device into use as a development target.
    • Responsibility for this area:
  • 9484 Packaging instructions (OBS): How to package an application in the OBS.
  • 9485 Packaging instructions (application SDK):How to package an application in the application SDK.
    • Responsibility for this area:
  • 9486 Publishing instructions: How to publish software.
    • Responsibility for this area:
  • 9487 Handset UX guidelines: User experience documentation for the handset vertical.
    • Responsibility for this area:
  • 9488 Netbook UX guidelines: User experience documentation for the netbook vertical.
    • Responsibility for this area: Elliot?
  • 9489 Architectural overview: Architectural overview of the MeeGo software platform.
    • Responsibility for this area:
  • 9490 API reference (MeeGo API): API reference documentation for the future-proof MeeGo API interfaces.
    • Responsibility for this area:
  • 9491 API reference (Platform API): API reference documentation for the potentially unstable platform interfaces.
    • Responsibility for this area:
  • 9492 Sample Applications: IDE shall provide a set of sample applications. Each sample shall be buildable using both the application SDK and an OBS instance, each sample shall be usable on the supported set of execution environments (with deficiencies explicitly listed, if some functionality is not available). Each sample shall be covered with a license that enables building both open source and commercial software based upon it.
    • Responsibility for this area: Ville?
  • 9493 Other documentations: Shall provide some documents like How to install and setup SDK, 'Hello World", Sample applications, FAQ, Debuging and performance tunning, How to build MeeGo image/QEMU image: To be divided into separate features to facilitate tracking?
    • Responsibility for this area: Taru and Elliot
  • 12241 Glossary: Create a glossary with relevant terms for MeeGo 1.2 SDK. Use the Glossary for MeeGo 1.1 (http://wiki.meego.com/SDK/Docs/1.1/Terminology) as the basis and update accordingly. //added by Taru on 11 January.//
    • Responsibility for this area: Taru

New features (to be added to Bugzilla during week 2)

  • Release notes
    • Responsibility for this area: Veli, Bob
  • Download site
    • Responsibility for this area: Veli, Bob
  • Troubleshooting
    • Responsibility for this area: Taru and Elliot
  • Glossary
    • Responsibility for this area: Taru
  • Using OBS server through Web interface (community) ): To be discussed with Tero Kojo what would be the best way to kick-start the cooperation with the community.
    • Responsibility for this area: Taru (with Tero Kojo)
  • Links to relevant Qt documentation.
    • Responsibility for this area: Taru
  • MeeGo development best practices (community)
    • Responsibility for this area: Taru and Ville
  • WRT instructions (is this needed?) - not really core, as WRT is a platform API and effectively deprecated for MeeGo -- Elliot Smith 11:26, 12 January 2011 (UTC)
    • Responsibility for this area: Elliot?
  • Qt Simulator instructions (is this needed?)
    • Responsibility for this area: Elliot?

Live BugzillaReports on SDK docs features

It is possible to show a live lookup of SDK docs issues in the wiki: view the page source to see the required code.

Features

IDStatusAssigneeSeverityVersionSummary (13 tasks)
9402*
9402 Need more information regarding all talks in the workflow (what are the tasks involved in workflow).
REOPENEDvelienhancement1.2[FEA] Command line environment
8469*
8469 Move to MeeGo feature list
NEWbspencerenhancement1.2[FEA] Feature request about "Delete Project" in Qt Creator
8470*
8470

http://meego.gitorious.org/meego-developer-tools/madde/commit/4c20f636e3afe2a85d6f8de58bde9c1d18860c31

fixes this bug ('mad-admin remove (-f|-n) all' implemented).

I cannot change 'Status:' though.
NEWtooenhancement1.2[FEA] Remove all the targets/runtimes with one mad-admin command
11386*
11386

I get the message blew too: Starting QEMU runtime meego-netbook-ia32-qemu-1.1.20101031.2037-sda-runtime This may take some time ...

but I had qemu-gl installed and in my PC /usr/lib/madde/linux-i686/runtimes/meego-handset-ia32-qemu-1.1.2-runtime/information contains :

 1 qemu='/usr/lib/madde/linux-i686/tools/qemu-meego/bin/qemu-meego'
 2 qemu_path_native='/usr/lib/madde/linux-i686/tools/qemu-meego/bin/qemu-meego'
 3 libpath='LD_LIBRARY_PATH=/usr/lib/madde/linux-i686/tools/qemu-meego/lib'
 4 qemu_args='-hda meego-handset-ia32-qemu-1.1.20110110.1026-sda.raw -name      MeeGo -m 1024 -boot c -enable-kvm -vga std -enable-gl -device virtio-gl-p    ci -soundhw ac97 -skin /opt/meego/qemu-gl/share/qemugl/meego/skin/handset/skin.xml -usbdevice tablet -net nic -net user,hostfwd=tcp:127.0.0.1:666   6-:22,hostfwd=tcp:127.0.0.1:13219-:13219,hostfwd=tcp:127.0.0.1:14168-:14168'
 5 ip='127.0.0.1'
 6 sshport='6666'
 7 redirport2='13219'
 8 redirport3='14168'

not same as yours.

And when I try to run qemugl like : sudo /opt/meego/qemu-gl/bin/qemugl I get

Could not initialize SDL - exiting

What should I do ? Thanks.
NEWzhiyuanenhancementunspecified[FEA] Madde/QT Creator should report error if QEMU was not started successfully
11644*
11644 Moving to SDK Features context
NEWbspencercriticalunspecified[FEA] Request enable USB ethernet driver for real device debugging in MeeGo SDK
12794*
12794

BUILD IMAGE meego-sdk-1.2-0123-2

HARDWARE MODEL: Windows XP, 32 bit

BUG DETAILED DESCRIPTIONS
===========================================================
Once you install the meego-sdk executable package you cannot just execute the QtCreator and start developing application. You need to enter the command-line and start downloading sysroot and run-environments

EXACT STEPS LEADING TO PROBLEM:
===========================================================
1. Install meego-sdk by using the executable file 2. Open QtCreator


EXPECTED OUTCOME:
===================
You should have a GUI menu which you can use to install/remove sysroots/targets rather than having to use the command-line strictly.

ACTUAL OUTCOME:
===================
No such menu exists

USER IMPACT:
===================

Users cannot use the QtCreator directly, they need to read the tutorial and enter command-line. Otherwise they won't know why it does not work (make command fails)
NEWlavonardoenhancementunspecified[FEA] Possibility of installing sysroot/run-environment from QtCreator GUI interface
13086*
13086

Compiling MTF Applications for the Qt Simulator is out of scope. Qt Components should rather be the way to create your applications.

Also note that MTF is not part of the core API set.
NEWmauriceknormalunspecified[FEA] Qt Simulator doesn't support MTF applications
13148*
13148

Hmm

I have to check the behaviour...

Yes. files paths must start with / (if not, ignored silently :( )

I think the glob patterns are not fully accepted, but just plain '*'.

I'll check and fix these (in near future).
NEWtoomajorunspecified[FEA] The rrpmbuild script should be able to figure out which files to put into the package.
13159*
13159

BUG DETAILED DESCRIPTIONS
===========================================================
EXACT STEPS LEADING TO PROBLEM: (Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message Connection Failed appears))
===========================================================
1. Install Meego SDK 2. Install Intel AppUP cross compiler (we did this on a Linux host) 3. Start Qt Creator by executing /opt/intel/appup-meego-tools/icc-meego-<version>/bin/launch_sdk.sh (this sets the environment for icc) 4. Build a default Meego Touch Framework Application w/ default g++ - this should work. 5. Switch to the Intel compiler. Change the Build Settings->qmake command line and add -spec linux-icc-v12 6. Build with the Intel compiler. Rebuild All.


EXPECTED OUTCOME:
===================
Expected outcome is that compilation and rpm packaging should work.

ACTUAL OUTCOME:
===================
Instead: the compiler reports that it cannot find MApplication and compilation fails.

USER IMPACT:
===================
REPRODUCIBILITY: (always, less than 1/10, 5/10, 9/10)
=====================================
Always.

EXTRA SOFTWARE INSTALLED:
============================
Intel AppUP-MeeGo-Tools SDK

OTHER COMMENTS:
===================
The issue is that the sample has some include directories specified with the full path to the sysroot and some without. -I/usr/lib/madde/linux-i686/meego-tablet-ia32-madde-sysroot-1.1.80.9.20101207.1-fs/usr/include/qt4/QtCore for example has a full path (as do many others). -I/usr/include/meegotouch is specified, but really needs to be -I/usr/lib/madde/linux-i686/meego-tablet-ia32-madde-sysroot-1.1.80.9.20101207.1-fs/usr/include/meegotouch.

This may be a 'feature', but as an aside it leads to the fact that the pretty printer inside of Qt Creator doesn't know where the include is located. Notice the squiggly lines under the #include <MApplication> - this means Qt Creator doesn't know where the file is located and cannot do things like argument completion inside of the GUI.

The fix will most likely be one of two things: 1) Fix all of the samples/wizards so they use the full path or 2) help icc get all of these paths preprended the same way g++ is able to do so (something in Qt Creator's Toolchain class perhaps?).
NEWbspencercriticalunspecified[FEA] Meego API includes cannot be seen by Intel Compiler
13604*NEWbspencernormal1.3[FEA] User should be able to select entire folder or multiple files for removal
15979*
15979

BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - MeeGo SDK 1.3 preview

HARDWARE MODEL (on what HW this bug is uncovered): IA-32

BUG DETAILED DESCRIPTIONS
===========================================================
Feature Request for DPD Tools. The AppUp SDK Suite for MeeGo superinstaller will install a set of libraries, compiler qmake.conf, and library .prf files into defined locations of the sysroot. At installation time, we will do this for all sysroots already installed on the host.

When users employ MADDE (or the visual package manager) to install new sysroots to the host, we need a method of copying these same libs, qmake.conf, and .prf files to the newly installed sysroot.

DPD will provide a document specifying the precise files and default from/to locations of the files at a later agreed upon date.


EXPECTED OUTCOME:
===================
A design, agreement on design, schedule and implementation for the feature.

ACTUAL OUTCOME:
===================
USER IMPACT:
===================
Important. We desire a user invisible method for copying these files to new sysroots. A fallback is to provide a script that the user would manually invoke after adding a sysroot, however this is undesirable.

REPRODUCIBILITY: (always, less than 1/10, 5/10, 9/10)
=====================================
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:


===================
NEWbspencerenhancementunspecified[FEA] Support to copy DPD tools configuration to installed sysroot/toolchains
16564*
16564

BUILD IMAGE(X.X.XX.X.XXXXXXXX.X - (e.g.: meego-netbook-ia32-1.0.90.0.20100831.1)):

HARDWARE MODEL (on what HW this bug is uncovered):

BUG DETAILED DESCRIPTIONS
===========================================================
EXACT STEPS LEADING TO PROBLEM: (Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message Connection Failed appears))
===========================================================
1.Current MeeGo SDK only provide the MADDE target and runtime image in tablet, handset and netbook. Customer can't run QEMU to simulate IVI home UX when they develop their application. 2. 3. 4. 5.

EXPECTED OUTCOME:
===================
Add IVI target and runtime image when using madde

ACTUAL OUTCOME:
===================
No image can't install relate to IVI

USER IMPACT:
===================
No Target to compile application within Qt creator, No image to run in QEMU simulate IVI home

REPRODUCIBILITY: (always, less than 1/10, 5/10, 9/10)
=====================================
EXTRA SOFTWARE INSTALLED:
============================
OTHER COMMENTS:


===================
NEWbspencerenhancementunspecified[FEA] Provide IVI target/runtime image in SDK
17968*
17968

DESCRIPTION OF FEATURE:
========================
AppUp SDK provides a set of head files and static libraries.

The Qt Creator of MeeGo SDK should be able to include and link to AppUp SDK header files and libraries which is NOT installed in MeeGo SDK target / sysroot folder.


DETAILED LIST OF PACKAGES:
===========================
PKG-NAME: PKG-VERSION: PKG-MAINTAINER: LICENSE: URL: SUMMARY DESCRIPTION:


OTHER COMMENTS:


===================
NEWbspencercriticalunspecified[FEA] Support interoperability with AppUp SDK which is NOT installed in target / sysroot folder

Bugs

no bugzilla tickets were found
Personal tools