Eclipse integration/Known issues - Revision history

imported_>amigadave: wikify slightly

2010-05-12T08:10:04Z

wikify slightly

imported_>dneary: Eclipse integration/KnownIssues final moved to Eclipse integration/Known issues: Capitalisation

2010-04-26T09:12:31Z

Eclipse integration/KnownIssues final moved to Eclipse integration/Known issues: Capitalisation

← Older revision	Revision as of 09:12, 26 April 2010
(No difference)

192.100.124.218: /* Maemo PC Connectivity */

2010-01-04T14:11:36Z

Maemo PC Connectivity

← Older revision		Revision as of 14:11, 4 January 2010
Line 76:		Line 76:
	** 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 Cygwin 1.7 SSHD service		** 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 Cygwin 1.7 SSHD service
	*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.		*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.
	** SSHFS may not be usable for "normal" user account. This is because /dev/fuse is not writable by default for "normal" users. /dev/fuse is usually writable only for group "fuse"		* SSHFS may not be usable for "normal" user account. This is because /dev/fuse is not writable by default for "normal" users. /dev/fuse is usually writable only for group "fuse"
	*** workaround is to add user account used to "fuse" group		** workaround is to add user account used to "fuse" group

	== Maemo SDK Virtual Images ==		== Maemo SDK Virtual Images ==

192.100.124.218: /* Maemo PC Connectivity */

2010-01-04T14:10:46Z

Maemo PC Connectivity

← Older revision		Revision as of 14:10, 4 January 2010
Line 76:		Line 76:
	** 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 Cygwin 1.7 SSHD service		** 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 Cygwin 1.7 SSHD service
	*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.		*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.
			** SSHFS may not be usable for "normal" user account. This is because /dev/fuse is not writable by default for "normal" users. /dev/fuse is usually writable only for group "fuse"
			*** workaround is to add user account used to "fuse" group

	== Maemo SDK Virtual Images ==		== Maemo SDK Virtual Images ==

192.100.124.218: /* Maemo PC Connectivity */

2010-01-04T10:39:25Z

Maemo PC Connectivity

← Older revision		Revision as of 10:39, 4 January 2010
Line 59:		Line 59:
	** 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)
			** Fremantle SDK does not support CPU Transparency
			*** workaround is to build and install new SBRSH client manually inside Scratchbox

	* 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

imported_>jatikka: /* Product configuration */

2009-12-23T07:58:56Z

Product configuration

← Older revision		Revision as of 07:58, 23 December 2009
Line 20:		Line 20:
	* 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/2nd_edition/) for VNC client to work on host PC		* Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Maemo device from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/) for VNC client to work on host PC

	== Maemo Mica plugin framework for Eclipse ==		== Maemo Mica plugin framework for Eclipse ==

imported_>jatikka: /* Product configuration */

2009-12-23T07:58:23Z

Product configuration

← Older revision		Revision as of 07:58, 23 December 2009
Line 20:		Line 20:
	* 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/2nd_edition/~~main.html#SECTION00030000000000000000~~) 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/2nd_edition/) for VNC client to work on host PC

	== Maemo Mica plugin framework for Eclipse ==		== Maemo Mica plugin framework for Eclipse ==

imported_>jatikka: /* Known Issues for Maemo Eclipse Integration Edition 2 Final release */

2009-12-23T06:34:51Z

Known Issues for Maemo Eclipse Integration Edition 2 Final release

← Older revision		Revision as of 06:34, 23 December 2009
Line 1:		Line 1:
	= Known Issues for Maemo Eclipse Integration Edition 2 Final release =		= Known Issues for Maemo Eclipse Integration Edition 2 Final release (R2.0.0) =

	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/.

imported_>jatikka: /* Maemo SDK Virtual Images */

2009-12-22T08:52:38Z

Maemo SDK Virtual Images

← Older revision		Revision as of 08:52, 22 December 2009
Line 84:		Line 84:

	* 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.		* 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.
	** workaround is to manually reconfigure network changes to the ~~Virtualization~~ Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes		** workaround is to manually reconfigure network changes to the Virtualisation Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes

	== Maemo Flasher-3.5 Tool ==		== Maemo Flasher-3.5 Tool ==

imported_>jatikka: A lot of small issues cleaned up for final releae

2009-12-22T08:48:27Z

A lot of small issues cleaned up for final releae

← Older revision		Revision as of 08:48, 22 December 2009
Line 5:		Line 5:
	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.		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.		Release Notes are here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_final.

	== Product baselines ==		== Product baselines ==
Line 17:		Line 17:

	* 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 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		* 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

Line 23:		Line 25:
	* none (so far :)		* none (so far :)

	== Maemo ESbox ~~plugin~~ for Eclipse ==		== Maemo ESbox 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.		** 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 missing packages for C/C++, Python and Qt 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 missing packages for C/C++, Python and Qt to the Maemo SDK and Maemo device.

	* Maemo Diablo SDK has ARMEL debugging problems when using Ubuntu Karmic host PC. If Maemo Diablo SDK is installed to Ubuntu Karmic environment native-gdb script will not work but gives segment fault which prevents debugging operations on Maemo SDK ARMEL rootstrap.		* Maemo Diablo SDK has ARMEL debugging problems when using Ubuntu Karmic host PC. If Maemo Diablo SDK is installed to Ubuntu Karmic environment native-gdb script will not work but gives segment fault which prevents debugging operations on Maemo SDK ARMEL rootstrap.
	** ~~See~~ more details from this bug report https://bugs.maemo.org/show_bug.cgi?id=7106		** see more details from this bug report https://bugs.maemo.org/show_bug.cgi?id=7106

	== Maemo PluThon ~~plugin~~ for Eclipse ==		== Maemo PluThon 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 57:		Line 59:
	** 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 ~~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.
			* WLAN connection may get broken if WLAN and USB Networking are used 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 ~~reflash~~ Maemo device or manually assign IP number to the connection (which may cause problems with DHCP)		** workaround is to re-flash 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
Line 69:		Line 75:
	*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.		*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.

	== Maemo SDK Virtual ~~Image~~ ==		== Maemo SDK Virtual Images ==

			* By default NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems
			** workaround is to update resolv.conf file for Scratchbox manually after Maemo SDK installation and/or after network changes

	* 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".		** workround is to use VMWare Player version 2.5.x or use only Bridged network mode for Maemo SDK Virtual Image

			* 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.
			** workaround is to manually reconfigure network changes to the Virtualization Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes

	== Maemo Flasher-3.5 Tool ==		== Maemo Flasher-3.5 Tool ==
Line 81:		Line 92:
	== 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 publicly 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

← Older revision		Revision as of 08:10, 12 May 2010
Line 3:		Line 3:
	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 ~~http~~:~~//wiki.maemo.org/Eclipse_integration~~.		Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here: [[Eclipse integration]].

	Release Notes are ~~here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_final~~.		[[Eclipse_integration/ReleaseNotes_final\|Release Notes are available]].

	== Product baselines ==		== Product baselines ==
Line 17:		Line 17:

	* 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 Maemo device from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/) for VNC client to work on host PC		* Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Maemo device from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/) 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 :)

Line 28:		Line 27:

	* 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.		** 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 missing packages for C/C++, Python and Qt 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 missing packages for C/C++, Python and Qt to the Maemo SDK and Maemo device.
			* Maemo Diablo SDK has ARMEL debugging problems when using Ubuntu Karmic host PC. If Maemo Diablo SDK is installed to Ubuntu Karmic environment <code>native-gdb</code> script will not work but gives segment fault which prevents debugging operations on Maemo SDK ARMEL rootstrap.
	* Maemo Diablo SDK has ARMEL debugging problems when using Ubuntu Karmic host PC. If Maemo Diablo SDK is installed to Ubuntu Karmic environment native-gdb script will not work but gives segment fault which prevents debugging operations on Maemo SDK ARMEL rootstrap.
	** see more details from this bug report https://bugs.maemo.org/show_bug.cgi?id=7106		** see more details from this bug report https://bugs.maemo.org/show_bug.cgi?id=7106

Line 44:		Line 40:
	== Maemo PC Connectivity ==		== Maemo PC Connectivity ==

	* Maemo PC Connectivity functionality with N900 device and Fremantle is more limited than with N800/N810 device with Diablo		* Maemo PC Connectivity functionality with [[Nokia N900\|N900]] device and [[Open development/Maemo roadmap/Fremantle\|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 61:		Line 57:
	** Fremantle SDK does not support CPU Transparency		** Fremantle SDK does not support CPU Transparency
	*** workaround is to build and install new SBRSH client manually inside Scratchbox		*** workaround is to build and install new SBRSH client manually inside Scratchbox

	* 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 are used simultaneously. Connection problems may occur after some time (can take hours or days) when device is (re)started and WLAN tries to connect.		* WLAN connection may get broken if WLAN and USB Networking are used 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 re-flash Maemo device or manually assign IP number to the connection (which may cause problems with DHCP)		** workaround is to re-flash 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
Line 83:		Line 75:
	* By default NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems		* By default NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems
	** workaround is to update resolv.conf file for Scratchbox manually after Maemo SDK installation and/or after network changes		** workaround is to update resolv.conf file for Scratchbox manually after Maemo SDK installation and/or after network changes

	* 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)
	** workround is to use VMWare Player version 2.5.x or use only Bridged network mode for Maemo SDK Virtual Image		** workround is to use VMWare Player version 2.5.x or use only Bridged network mode for Maemo SDK Virtual Image

	* 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.		* 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.
	** workaround is to manually reconfigure network changes to the Virtualisation Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes		** workaround is to manually reconfigure network changes to the Virtualisation Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes
Line 97:		Line 87:

	* Some publicly 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 publicly 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