Editing Eclipse integration/Known issues
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | = Known Issues for Maemo Eclipse Integration Edition 2 Final release | + | = Known Issues for Maemo Eclipse Integration Edition 2 Final release = |
More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/. | More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/. | ||
- | Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here: | + | Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here http://wiki.maemo.org/Eclipse_integration. |
- | + | Release Notes file is here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_final. | |
== Product baselines == | == Product baselines == | ||
Line 18: | Line 18: | ||
* Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications | * Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications | ||
* Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC | * Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC | ||
- | * Diablo 4.1.2 device requires hildon-desktop patch to be installed to the | + | * Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Tablet from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/main.html#SECTION00030000000000000000) for VNC client to work on host PC |
== Maemo Mica plugin framework for Eclipse == | == Maemo Mica plugin framework for Eclipse == | ||
- | |||
* none (so far :) | * none (so far :) | ||
- | == Maemo ESbox for Eclipse == | + | == Maemo ESbox plugin for Eclipse == |
* Hover help for Python does not work on ESBox because documentation has not been integrated. | * Hover help for Python does not work on ESBox because documentation has not been integrated. | ||
+ | |||
* Installing Nokia binaries may sometimes fail with exit code 100 when Maemo SDK gets installed. | * Installing Nokia binaries may sometimes fail with exit code 100 when Maemo SDK gets installed. | ||
- | ** | + | ** Workaround is to restart the Maemo SDK binary installation until it goes through without errors. |
+ | |||
* If during Maemo SDK installation to other than Debian based Linux operating systems the default options for Maemo SDK Virtual image installation wizard are chosen and Nokia binaries installation fails, wizard proceeds normally to end (installing Development Environments for C/C++, Python and Qt). If you choose to cancel the installation because failed Nokia binaries Development Environments are not installed properly to the Maemo SDK and Maemo device. | * If during Maemo SDK installation to other than Debian based Linux operating systems the default options for Maemo SDK Virtual image installation wizard are chosen and Nokia binaries installation fails, wizard proceeds normally to end (installing Development Environments for C/C++, Python and Qt). If you choose to cancel the installation because failed Nokia binaries Development Environments are not installed properly to the Maemo SDK and Maemo device. | ||
- | ** | + | ** Workaround is to select '''Project -> Validate Installed Packages''' from Eclipse IDE which verifies the integrity of installed development environments and re-installs possible missing packages for C/C++, Python and Qt to the Maemo SDK and Maemo device. |
- | + | ||
- | + | ||
- | == Maemo PluThon for Eclipse == | + | == Maemo PluThon plugin for Eclipse == |
* Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated | * Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated | ||
Line 40: | Line 39: | ||
== Maemo PC Connectivity == | == Maemo PC Connectivity == | ||
- | * Maemo PC Connectivity functionality with | + | * 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 | ** N900 will not support USB host mode | ||
*** no workaround (N900 HW issue) | *** no workaround (N900 HW issue) | ||
Line 55: | Line 54: | ||
** Fremantle platform and SDK support ONLY 16-bit color depth for X Server | ** 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) | *** 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 | * 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 errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" may happen when SBRSH is used first time with Maemo device (for example after device flashing when SSH keys need to be reset). | * When creating a project and setting SBRSH as download method errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" may happen when SBRSH is used first time with Maemo device (for example after device flashing when SSH keys need to be reset). | ||
** workaround is to restart Maemo device. | ** workaround is to restart Maemo device. | ||
- | * WLAN connection may get broken if WLAN and USB Networking | + | * WLAN connection may get broken if using WLAN and USB Networking simultaneously. Connection problems may occur after some time (can take hours or days) when device is (re)started and WLAN tries to connect. |
** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error | ** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error | ||
- | ** workaround is to | + | ** workaround is to reflash Maemo device or manually assign IP number to the connection (which may cause problems with DHCP) |
* Windows 7 (and Vista) support is only beta level because Cygwin 1.7 (first Cygwin release to support Windows 7 and Vista) is on beta level (Windows XP with Cygwin 1.5 is fully supported) | * Windows 7 (and Vista) support is only beta level because Cygwin 1.7 (first Cygwin release to support Windows 7 and Vista) is on beta level (Windows XP with Cygwin 1.5 is fully supported) | ||
** Cygwin 1.7 beta installation may require manual configuration for Maemo | ** Cygwin 1.7 beta installation may require manual configuration for Maemo | ||
** Cygwin 1.7 beta X11 may crash when Maemo applications are run with it | ** Cygwin 1.7 beta X11 may crash when Maemo applications are run with it | ||
- | ** Host PC Connectivity does not install if Vista or Windows 7 machine is part of Windows Domain because it fails to create new user for | + | ** Host PC Connectivity does not install if Vista or Windows 7 machine is part of Windows Domain because it fails to create new user for SSHD service |
- | + | ||
- | + | ||
- | + | ||
- | == Maemo SDK Virtual | + | == 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 |
- | + | ||
* VMWare Player version 3.0 may have problems to keep ssh connection live in NAT mode (notice that VMWare Player 2.5 or Bridged mode works fine) | * VMWare Player version 3.0 may have problems to keep ssh connection live in NAT mode (notice that VMWare Player 2.5 or Bridged mode works fine) | ||
- | + | * Changing network configuration after installation of VMWare, VirtualBox or QEMu and Maemo SDK VIrtual Image may require reconfiguration of network also for the virtualisation environment and Maemo SDK. Usually, log in to the image and invoke "sudo dhclient". | |
- | * Changing network configuration after installation of VMWare, VirtualBox or | + | |
- | + | ||
== Maemo Flasher-3.5 Tool == | == Maemo Flasher-3.5 Tool == | ||
Line 86: | Line 77: | ||
== Integration testing == | == Integration testing == | ||
- | * Some | + | * 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 | * Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products | ||
Learn more about Contributing to the wiki.