Eclipse integration/Known issues prefinal

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
  • Automatic installation of OProfiling support to the Maemo device may cause Eclipse to crash if Eclipse cannot find OProfile packages from configured repositories. Add repository 
   deb http://repository.maemo.org/ diablo/tools free

to the Maemo device and run "sudo apt-get update" manually as workaround.

Maemo ESBox plugin for Eclipse

  • Some of the templates and examples provided by ESBox are not yet ported to Fremantle
  • 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
  • Remote ltrace tool launching for Maemo device fails if SBRSH is used
    • workaround is to use SSH and RSE instead of SBRSH
  • Python interpreter is not switched when switching targets
  • Configuring for C/C++ Indexing in Mac OS does not always work properly

Maemo Pluthon plugin for Eclipse

  • <none>

Maemo PC Connectivity

  • N900 device support with Fremantle is more limited on functionality point of view than N800/N810 device support with Diablo
    • N900 will not support USB host mode
    • 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
    • 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 plug-out and plug-in USB cable between mode changes
    • Fremantle platform does not have libicd-dummy package available until final release and thus user can not navigate to Internet through the browser using USB and BlueTooth. He/she will be able to navigate only using WLAN (standard behavior)
      • workaround final PC Connectivity release will have libicd-dummy package
  • 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 tool may have problems in some Windows host PC configurations to flash eMMC images properly. Workaround is to retry with another USB port in host PC or use Linux/Mac for eMMC flashing

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

Retrieved from "http://wiki.maemo.org/Eclipse_integration/Known_issues_prefinal"