Eclipse integration/Known issues prefinal

(Maemo Pluthon plugin for Eclipse)
(Maemo ESBox plugin for Eclipse)
Line 24: Line 24:
* Configuring C/C++ indexing in Mac OS X does not always work properly
* Configuring C/C++ indexing in Mac OS X does not always work properly
* Hover help for Python and C++ for Maemo API documents does not work on ESBox because documentation is not integrated yet
* Hover help for Python and C++ for Maemo API documents does not work on ESBox because documentation is not integrated yet
 +
* Debian installation packages creation for Python applications using Eclipse Wizard may fail to create correct structure for packages
== Maemo Pluthon plugin for Eclipse ==
== Maemo Pluthon plugin for Eclipse ==

Revision as of 06:02, 11 September 2009

Contents

Known Issues for Maemo Eclipse Integration Edition 2 PreFinal release

More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/.


Product baselines

  • Fremantle devices are not officially supported as devices do not exist (publicly) yet but most unofficial Fremantle packages are already available from Fremantle extras-devel repository

Product configuration

Maemo Mica plugin framework for Eclipse

  • While debugging Python application automatic termination of debugged program does not work when debugging session ends

Maemo ESBox plugin for Eclipse

  • Installation wizard for SDK Virtual Image on Mac OS X may run into deadlock in situations when more than one dialog is open at the same time
    • workaround is to use manual installation of SDK Virtual Image on Mac OS X
  • Configuring C/C++ indexing in Mac OS X does not always work properly
  • Hover help for Python and C++ for Maemo API documents does not work on ESBox because documentation is not integrated yet
  • Debian installation packages creation for Python applications using Eclipse Wizard may fail to create correct structure for packages

Maemo Pluthon plugin for Eclipse

  • Remote ltrace tool launching for Maemo device fails if SBRSH is used
    • workaround is to use SSH and RSE instead of SBRSH
  • Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated yet

Maemo PC Connectivity

  • Maemo PC Connectivity functionality with N900 device and Fremantle is more limited than with N800/N810 device with Diablo
    • N900 will not support USB host mode
      • no workaround (N900 HW issue)
    • N900 will not support IP Forwarding (iptable NAT kernel modules)
      • workaround is to rebuild Fremantle kernel with NAT enabled and hack kernel symbols for NAT kernel modules
    • N900 will not support BlueTooth connections simultaneously with WLAN connections
      • no known workaround
    • N900 will not support USB connectivity switching between "PC Suite" and "Mass Storage" modes with platform default applet (applet provided by PC Connectivity works fine)
      • workaround is to use ONLY configuration applet provided by PC Connectivity instead of default applet
      • another workaround is to plug-out and plug-in USB cable between mode changes with default applet
    • Fremantle platform does not have libicd-dummy package available until final release and thus user cannot navigate to Internet through the browser using USB and BlueTooth. He/she will be able to navigate only using WLAN (standard behavior)
      • final PC Connectivity release will have libicd-dummy package
    • Samba does not work with Fremantle platform and N900 causing disk mounts between N900 and Windows host PC to fail
      • will be (hopefully) fixed for final release
    • Fremantle platform and SDK support ONLY 16-bit color depth for X Server
      • workaround is to configure host PC X Server (in Windows and Mac OS X) to use 16-bit depth instead of default one (if default does not happen to be 16-bit)
  • Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems
  • When creating a project and setting SBRSH as download method quite often errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" happens. As a workaround you need to restart SBRSHD (on Maemo device side) and restart ESBox (on host PC side)

Maemo SDK Virtual Image

  • NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems

Maemo Flasher-3.5 Tool

  • Flasher-3.5 beta for Windows tool may have problems in some Windows host PC configurations to flash eMMC images properly
    • workaround is to use Linux or Mac Flasher-3.5 tool for eMMC flashing
  • Flasher-3.5 beta for Windows tool fails to unpack FIASCO image with '-u' option
    • workaround is to use Linux or Mac Flasher-3.5 tool for unpacking FIASCO images

Integration testing

  • Some publically available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published
  • Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products

Feedback can be sent to eclipse-integration@maemo.org