Eclipse integration/Known issues beta2

(Known Issues for Beta 2)
(wikify slightly)
 
(14 intermediate revisions not shown)
Line 1: Line 1:
-
= Known Issues for Maemo Eclipse Integration Edition 2 Beta 2 release =
+
= Known Issues for Maemo Eclipse Integration Edition 2 Beta 1 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/.
Line 6: Line 6:
== Product baselines ==
== Product baselines ==
-
* Fremantle SDK is supported as separate installation e.g. not delivered as default environment with Desktop image, for example.
+
* [[Open development/Maemo roadmap/Fremantle|Fremantle]] SDK is supported as separate installation e.g. not delivered as default environment with Desktop image, for example.
-
* Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle extras-devel repository
+
* Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle [[extras-devel]] repository
-
* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will be released couple of days AFTER Eclipse Integration Edition 2 Beta 1 release as it needs to include this Beta 1 release products :)
+
* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will not be created for the Beta 2 release but users of old Beta 1 Desktop image are able to upgrade environment to Beta 2 level with these instructions: http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html
 +
Notice that updating process from Eclipse Update Site (update from beta 1 to beta 2) may not work for some plug-ins
== Product configuration ==
== Product configuration ==
-
* Mac OS X does not yet have support for Linux porting framework like Windows has with Cygwin
 
-
* Pluthon does not yet have flasher integration for Windows or Mac OS X as there does not yet exist native Windows and Mac OS X flasher tools
 
* Maemo SDK ARMEL rootstrap is ment to be used only for cross-compiling and it does not support running or debugging applications
* Maemo SDK ARMEL rootstrap is ment 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 Tablet from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/beta1/installation.html) for VNC client to work on host PC
* 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/beta1/installation.html) for VNC client to work on host PC
-
* PyMaemo installation meta packages in Diablo extras repository (maemo-python-env and maemo-python-device-env) do not install python2.5-distutils as default dependency and thus installation package creation with setup.py may not work (this has been agreed to be fixed by PyMaemo project)
 
== Maemo Mica plugin framework for Eclipse ==
== Maemo Mica plugin framework for Eclipse ==
-
* Mica framework implementation will still change somewhat for the next Beta 2 release and because of that stability of Beta 1 release interfaces cannot be quaranteed (actually there WILL be many changes to Mica interfaces for Beta 2)
 
-
* Mica developer documentation is not yet in good enough level for developers to start using it as basis for their own maemo plugins
 
* While debugging Python application automatic termination of debugged program does not work when debugging session ends
* 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 <pre>deb http://repository.maemo.org/ diablo/tools free</pre> to the Maemo device and run "sudo apt-get update" manually as workaround.
== Maemo ESBox plugin for Eclipse ==
== Maemo ESBox plugin for Eclipse ==
-
* Launching X server for Diablo and Fremantle require two different X server instances (because of different startup parameters) and this has not been implemented yet
+
* Some of the templates and examples provided by ESBox are not yet ported to Fremantle
-
* There may be occasional SDK build problems for C/C++ components with "error: cannot run C compiled programs". It may help to restart Eclipse IDE and run startup and refresh to Scratchbox.
+
== Maemo Pluthon plugin for Eclipse ==
== Maemo Pluthon plugin for Eclipse ==
-
* Debian installation packages created on-device do not support uninstallation
+
* none
== Maemo PC Connectivity ==
== Maemo PC Connectivity ==
-
* Mac OS X support is initial for Beta 1 release on functionality and quality point of view. Especially testing on Mac environment has been somewhat limited.
+
* Mac OS X support is still initial for Beta 2 release on functionality and quality point of view. Especially testing on Mac environment has been somewhat limited.
-
* Configuring connectivity to work between Tablet and host PC after installation is still 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 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 ==
== 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
+
* NetworkManager is being started after Scratchbox, so the <code>resolv.conf</code> 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 ==
== 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
* 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
----
----
Feedback can be sent to eclipse-integration@maemo.org
Feedback can be sent to eclipse-integration@maemo.org
 +
 +
[[Category:Eclipse]]

Latest revision as of 08:16, 12 May 2010

Contents

[edit] Known Issues for Maemo Eclipse Integration Edition 2 Beta 1 release

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


[edit] Product baselines

  • Fremantle SDK is supported as separate installation e.g. not delivered as default environment with Desktop image, for example.
  • Fremantle devices are not officially supported as devices do not exist yet but first unofficial Fremantle packages are available from Fremantle extras-devel repository
  • Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) will not be created for the Beta 2 release but users of old Beta 1 Desktop image are able to upgrade environment to Beta 2 level with these instructions: http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html

Notice that updating process from Eclipse Update Site (update from beta 1 to beta 2) may not work for some plug-ins

[edit] Product configuration

[edit] 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.

[edit] Maemo ESBox plugin for Eclipse

  • Some of the templates and examples provided by ESBox are not yet ported to Fremantle

[edit] Maemo Pluthon plugin for Eclipse

  • none

[edit] Maemo PC Connectivity

  • Mac OS X support is still initial for Beta 2 release on functionality and quality point of view. Especially testing on Mac environment has been somewhat limited.
  • 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)

[edit] 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

[edit] 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

[edit] 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 "https://wiki.maemo.org/Eclipse_integration/Known_issues_beta2"