Setting up the development environment - Revision history

Atzebadekappe: veralteten link überarbeitet

2010-11-19T16:53:49Z

veralteten link überarbeitet

← Older revision		Revision as of 16:53, 19 November 2010
Line 48:		Line 48:
	## Install Subclipse per [http://subclipse.tigris.org/install.html these instructions]. You can combine this step with the previous one.		## Install Subclipse per [http://subclipse.tigris.org/install.html these instructions]. You can combine this step with the previous one.
	# Exit Eclipse		# Exit Eclipse
	# Download the Wireless Toolkit 2.2 from ~~http~~://~~java~~.sun.com/~~products~~/~~sjwtoolkit~~/~~download~~-~~2_2.html (the file is called~~ <code>~~j2me_wireless_toolkit~~-~~2_2~~-~~linux-i386~~.bin</code>		# Download the Wireless Toolkit 2.2 from (the file is called https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewFilteredProducts-SingleVariationTypeFilter<code>sun_java_wireless_toolkit-2.5.2_01-linuxi486.bin.sh</code>
	# <code>chmod a+x ~~j2me_wireless_toolkit~~-~~2_2~~-~~linux-i386~~.bin</code>		# <code>chmod a+x sun_java_wireless_toolkit-2.5.2_01-linuxi486.bin.sh</code>
	# <code>./~~j2me_wireless_toolkit~~-~~2_2~~-~~linux-i386~~.bin</code>		# <code>./sun_java_wireless_toolkit-2.5.2_01-linuxi486.bin.sh</code>
	# If it should ask you for the path to a "Java interpreter directory": Find out where the <code>java</code> binary lives (in another terminal do <code>which java</code> which will say something like <code><var>/usr/bin/</var>java</code>, where <code><var>/usr/bin/</var></code> is the 'Java interpreter directory').		# If it should ask you for the path to a "Java interpreter directory": Find out where the <code>java</code> binary lives (in another terminal do <code>which java</code> which will say something like <code><var>/usr/bin/</var>java</code>, where <code><var>/usr/bin/</var></code> is the 'Java interpreter directory').
	# Install the toolkit somewhere below your home directory (for example <code>/home/<var>ploetz</var>/<var>sw/WTK2.2</var></code>)		# Install the toolkit somewhere below your home directory (for example <code>/home/<var>ploetz</var>/<var>sw/WTK2.2</var></code>)

Fabalint: /* Installation for Windows */ like on linux> eclipseme fixed the docs :)

2006-10-25T00:54:02Z

Installation for Windows: like on linux> eclipseme fixed the docs :)

← Older revision		Revision as of 00:54, 25 October 2006
Line 26:		Line 26:
	# Install Subversion: http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 (the svn-1.2.3-setup.exe)		# Install Subversion: http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 (the svn-1.2.3-setup.exe)
	# Adjust the rights on <code><var>c:\eclipse</var></code> to Everybody: Read, Execute (make sure these are inherited to all files and folders below)		# Adjust the rights on <code><var>c:\eclipse</var></code> to Everybody: Read, Execute (make sure these are inherited to all files and folders below)
	# Run Eclipse and install EclipseME per [http://eclipseme.org/docs/installEclipseME.html these] installation instructions (Note: the ~~correct~~ ~~update~~ ~~site~~ is <code>http://www.eclipseme.org/updates/</code> and <em>not</em> <code>http://eclipseme.sourceforge.net/updates/</code> which erroneously is shown in the screenshots.) Don't bother with the configuration instructions yet.		# Run Eclipse and install EclipseME per [http://eclipseme.org/docs/installEclipseME.html these] installation instructions (Note: they fixed the documentation to point to <code>http://www.eclipseme.org/updates/</code> and <em>not</em> <code>http://eclipseme.sourceforge.net/updates/</code> which erroneously was shown in the screenshots.) Don't bother with the configuration instructions yet.
	# Install Subclipse per [http://subclipse.tigris.org/install.html these instructions]. You can combine this step with the previous one.		# Install Subclipse per [http://subclipse.tigris.org/install.html these instructions]. You can combine this step with the previous one.
	# Exit Eclipse.		# Exit Eclipse.

Fabalint: /* Installation for Linux */ - updated the page in the documentation of eclipseme

2006-10-25T00:52:19Z

Installation for Linux: - updated the page in the documentation of eclipseme

← Older revision		Revision as of 00:52, 25 October 2006
Line 45:		Line 45:
	# Install subversion by whatever method your distribution uses (Gentoo Linux: <code>emerge subversion</code>)		# Install subversion by whatever method your distribution uses (Gentoo Linux: <code>emerge subversion</code>)
	# Start Eclipse		# Start Eclipse
	## Install EclipseME per [http://eclipseme.org/docs/installEclipseME.html these] installation instructions (Note: the ~~correct~~ ~~update~~ ~~site~~ is <code>http://www.eclipseme.org/updates/</code> and <em>not</em> <code>http://eclipseme.sourceforge.net/updates/</code> which erroneously is shown in the screenshots.) Don't bother with the configuration instructions yet.<br>Note: If you did not install Eclipse in your home directory you may have to use the <code>Change Location...</code> button to choose an installation location where you can write to.		## Install EclipseME per [http://eclipseme.org/docs/installEclipseME.html these] installation instructions (Note: they fixed the documentation to point to <code>http://www.eclipseme.org/updates/</code> and <em>not</em> <code>http://eclipseme.sourceforge.net/updates/</code> which erroneously was shown in the screenshots.) Don't bother with the configuration instructions yet.<br>Note: If you did not install Eclipse in your home directory you may have to use the <code>Change Location...</code> button to choose an installation location where you can write to.
	## Install Subclipse per [http://subclipse.tigris.org/install.html these instructions]. You can combine this step with the previous one.		## Install Subclipse per [http://subclipse.tigris.org/install.html these instructions]. You can combine this step with the previous one.
	# Exit Eclipse		# Exit Eclipse

Henryk: /* Set up Bluetooth (Linux only) */

2005-12-20T05:21:16Z

Set up Bluetooth (Linux only)

@@ Line 83: / Line 83: @@
  export JDK_PLATFORM=linux
  make
-On Debian stable you might run into compilation problems mentioning some confusion of <code>uint8_t</code> and <code>char</code>, probably due to too old bluez-libs. You then should use the following patch:
+On Debian stable you might run into compilation problems mentioning some confusion of <code>uint8_t</code> and <code>char</code>, probably due to too old bluez-libs. You then should use [http://www.informatik.hu-berlin.de/~ploetz/avetana.diff this patch]. Use it like this:
  patch -p1 < ~/id/avetana.diff

Henryk: /* Common checkout instructions */

2005-12-17T21:11:38Z

Common checkout instructions

← Older revision		Revision as of 21:11, 17 December 2005
Line 57:		Line 57:
	==Common checkout instructions==		==Common checkout instructions==
	# Window -> Open Perspective -> SVN Repository Exploring		# Window -> Open Perspective -> SVN Repository Exploring
	# Right click in the SVN Repository view and choose New -> Repository Location. The URL shall be <code>svn://merkur//</code>, and fill in your username and password.		# Right click in the SVN Repository view and choose New -> Repository Location. The URL shall be <code>svn://merkur/</code>, and fill in your username and password.
	# On merkur, in the <code>span</code> subdirectory, you'll find three directories for now:		# On merkur, in the <code>span</code> subdirectory, you'll find three directories for now:
	#; Testbed : Contains the J2ME code for the mobile phone, and the common libraries		#; Testbed : Contains the J2ME code for the mobile phone, and the common libraries

Henryk: /* Common checkout instructions */

2005-12-16T09:09:05Z

Common checkout instructions

← Older revision		Revision as of 09:09, 16 December 2005
Line 63:		Line 63:
	#; docs : Documentation and illustrations		#; docs : Documentation and illustrations
	# Right click 'Testbed' and use Check out as project		# Right click 'Testbed' and use Check out as project
	#; Sony-Ericsson Toolkit : Open Window -> Preferences -> J2ME. Right click Profiles -> Add MIDP profile. Profile name "Bluetooth", Next, Add External JARs -> <code><var>C:\SonyEricsson</var>/J2ME_SDK/PC_Emulation/WTK2/lib/jsr082.jar</code>, Finish. Then expand Platform Definitions -> Sony Ericsson J2ME SDK 2.2.x MIDP Platform. Right click Platform Definitions, Add Platform Definition. Platform Definition name "Bluetooth Platform", Base Platform Definition "Sony Ericsson J2ME SDK 2.2.x MIDP Platform", Next, Configuration CLDC-1.1, add all Profiles that the Sony Ericsson J2ME SDK 2.2.x MIDP Platform has (that's why you just expanded it) and additionally the Bluetooth profile. Finish. Unfortunately this setting is not permanent and the current version of ~~eclipse~~ forgets about your choice of CLDC-1.1 as soon as you quit Eclipse. When restarting Eclipse you have to delete this platform definition and recreate it.		#; Sony-Ericsson Toolkit : Open Window -> Preferences -> J2ME. Right click Profiles -> Add MIDP profile. Profile name "Bluetooth", Next, Add External JARs -> <code><var>C:\SonyEricsson</var>/J2ME_SDK/PC_Emulation/WTK2/lib/jsr082.jar</code>, Finish. Then expand Platform Definitions -> Sony Ericsson J2ME SDK 2.2.x MIDP Platform. Right click Platform Definitions, Add Platform Definition. Platform Definition name "Bluetooth Platform", Base Platform Definition "Sony Ericsson J2ME SDK 2.2.x MIDP Platform", Next, Configuration CLDC-1.1, add all Profiles that the Sony Ericsson J2ME SDK 2.2.x MIDP Platform has (that's why you just expanded it) and additionally the Bluetooth profile. Finish. Unfortunately this setting is not permanent and the current version of EclipseME forgets about your choice of CLDC-1.1 as soon as you quit Eclipse. When restarting Eclipse you have to delete this platform definition and recreate it.
	# Go back to the Java perspective, right click the newly created project and open the J2ME settings. Set the J2ME Platform Definition to your custom-created Bluetooth Platform for the Sony Ericsson Toolkit, or to the J2ME Wireless Toolkit 2.2 MIDP 2.0 All Profiles Platform for the SUN toolkit. Ok.		# Go back to the Java perspective, right click the newly created project and open the J2ME settings. Set the J2ME Platform Definition to your custom-created Bluetooth Platform for the Sony Ericsson Toolkit, or to the J2ME Wireless Toolkit 2.2 MIDP 2.0 All Profiles Platform for the SUN toolkit. Ok.
	# Go back to the SVN Repository Exploring perspective, Right click 'jsr82test' and Check out as project.		# Go back to the SVN Repository Exploring perspective, Right click 'jsr82test' and Check out as project.

Henryk: /* Set up Bluetooth (Linux only) */

2005-12-16T09:05:14Z

Set up Bluetooth (Linux only)

← Older revision		Revision as of 09:05, 16 December 2005
Line 83:		Line 83:
	export JDK_PLATFORM=linux		export JDK_PLATFORM=linux
	make		make
			On Debian stable you might run into compilation problems mentioning some confusion of <code>uint8_t</code> and <code>char</code>, probably due to too old bluez-libs. You then should use the following patch:
			<pre>
			diff -rU 2 avetana_alt/sources/c/BlueZ.cpp avetana/sources/c/BlueZ.cpp
			--- avetana_alt/sources/c/BlueZ.cpp 2005-10-22 22:08:10.000000000 +0200
			+++ avetana/sources/c/BlueZ.cpp 2005-12-16 09:53:08.688229557 +0100
			@@ -176,5 +176,5 @@

			memset(&buf, 0, sizeof(sdp_buf_t));
			- buf.data = (uint8_t*)malloc(SDP_UUID_SEQ_SIZE);
			+ buf.data = (char*)malloc(SDP_UUID_SEQ_SIZE);
			buf.buf_size = SDP_UUID_SEQ_SIZE;

			@@ -1911,10 +1911,10 @@

			if (cstate_len > 0 \|\| rsp_concat_buf.data_size != 0) {
			- uint8_t *targetPtr = NULL;
			+ char *targetPtr = NULL;

			cstate = cstate_len > 0? (sdp_cstate_t *)(pdata + rsp_count): 0;

			// build concatenated response buffer
			- rsp_concat_buf.data = (uint8_t *)realloc(rsp_concat_buf.data, rsp_concat_buf.data_size + rsp_count);
			+ rsp_concat_buf.data = (char *)realloc(rsp_concat_buf.data, rsp_concat_buf.data_size + rsp_count);
			rsp_concat_buf.buf_size = rsp_concat_buf.data_size + rsp_count;
			targetPtr = rsp_concat_buf.data + rsp_concat_buf.data_size;
			@@ -2057,5 +2057,5 @@

			// build concatenated response buffer
			- rsp_concat_buf.data = (uint8_t *)realloc(rsp_concat_buf.data, rsp_concat_buf.data_size + rsp_count);
			+ rsp_concat_buf.data = (char *)realloc(rsp_concat_buf.data, rsp_concat_buf.data_size + rsp_count);
			targetPtr = (char *)rsp_concat_buf.data + rsp_concat_buf.data_size;
			rsp_concat_buf.buf_size = rsp_concat_buf.data_size + rsp_count;
			@@ -2428,5 +2428,5 @@
			uint64_t u64;
			uint128_t u128;
			- uint8_t *seqp = buf->data + buf->data_size;
			+ char *seqp = buf->data + buf->data_size;

			pdu_size = sdp_set_data_type(buf, dtd);
			</pre>
			Use it like this:
			patch -p1 < ~/id/avetana.diff

			Once you have successfully compiled the library you will get (among others) a file <code>build/libavetanaBT.so</code>. Place this in the <code>jsr82test/res</code> directory of your Eclipse workspace and you should be ready to use the Bluetooth code.

Henryk: /* Common checkout instructions */

2005-12-16T08:39:22Z

Common checkout instructions

← Older revision		Revision as of 08:39, 16 December 2005
Line 67:		Line 67:
	# Go back to the SVN Repository Exploring perspective, Right click 'jsr82test' and Check out as project.		# Go back to the SVN Repository Exploring perspective, Right click 'jsr82test' and Check out as project.

	You have checked out all the necessary code~~. To use the Avetana Bluetooth library just must place the <code>libavetanaBT.so</code> in <code>jsr82test/res</code>~~. To start your first MIDlet in the Java perspective: In the Package Explorer, expand Testbed -> src -> (default package). Right click <code>Test1.java</code> and choose Run as -> Emulated J2ME Midlet.		You now have checked out all the necessary code. To start your first MIDlet, in the Java perspective: In the Package Explorer, expand Testbed -> src -> (default package). Right click <code>Test1.java</code> and choose Run as -> Emulated J2ME Midlet.

			==Set up Bluetooth (Linux only)==
			Use your distribution preferred way to install the hotplug package (should already be installed by default) and the bluez-utils package (or whatever contains the <code>hcid</code> binary). On some distributions you will also need to install the corresponding development packages (libbluetooth1-dev in Debian, generally whatever contains the <code>bluetooth.h</code> file).

			Nowf ire up the init script that came with the bluez package (something like <code>/etc/init.d/bluez start</code>, may already have been done by your package manager) and plug in the Bluetooth USB adaptor. You should now see a device <code>hci0</code> in the output of <code>hciconfig</code> and be able to do <code>hcitool scan</code> to scan for the mobile phone (or any other Bluetooth device).

			Download the source for the Avetana JSR-82 package from their [http://sourceforge.net/projects/avetanabt/ sourceforge.net project page]. Unpack the package:
			mkdir avetana
			cd avetana
			tar -xzf ~/id/avetanaBluetooth-200510223.tgz
			and compile it:
			cd sources
			export JDK_HOME=<var>/opt/sun-jdk-1.4.2.09</var>
			export JDK_PLATFORM=linux
			make

Henryk: /* Common checkout instructions */

2005-12-15T11:14:22Z

Common checkout instructions

← Older revision		Revision as of 11:14, 15 December 2005
Line 68:		Line 68:

	You have checked out all the necessary code. To use the Avetana Bluetooth library just must place the <code>libavetanaBT.so</code> in <code>jsr82test/res</code>. To start your first MIDlet in the Java perspective: In the Package Explorer, expand Testbed -> src -> (default package). Right click <code>Test1.java</code> and choose Run as -> Emulated J2ME Midlet.		You have checked out all the necessary code. To use the Avetana Bluetooth library just must place the <code>libavetanaBT.so</code> in <code>jsr82test/res</code>. To start your first MIDlet in the Java perspective: In the Package Explorer, expand Testbed -> src -> (default package). Right click <code>Test1.java</code> and choose Run as -> Emulated J2ME Midlet.
	[[Link title]]

Henryk at 11:13, 15 December 2005

2005-12-15T11:13:49Z

← Older revision		Revision as of 11:13, 15 December 2005
Line 1:		Line 1:
			[[Category:SPAN]]
	The development environment for the SPAN project involves:		The development environment for the SPAN project involves:
	* A Wireless Toolkit: Either from [http://developer.sonyericsson.com/site/global/docstools/java/p_java.jsp Sony Ericsson] (windows-only) or from [http://java.sun.com/products/sjwtoolkit/ SUN] (Linux or Windows)		* A Wireless Toolkit: Either from [http://developer.sonyericsson.com/site/global/docstools/java/p_java.jsp Sony Ericsson] (windows-only) or from [http://java.sun.com/products/sjwtoolkit/ SUN] (Linux or Windows)
Line 67:		Line 68:

	You have checked out all the necessary code. To use the Avetana Bluetooth library just must place the <code>libavetanaBT.so</code> in <code>jsr82test/res</code>. To start your first MIDlet in the Java perspective: In the Package Explorer, expand Testbed -> src -> (default package). Right click <code>Test1.java</code> and choose Run as -> Emulated J2ME Midlet.		You have checked out all the necessary code. To use the Avetana Bluetooth library just must place the <code>libavetanaBT.so</code> in <code>jsr82test/res</code>. To start your first MIDlet in the Java perspective: In the Package Explorer, expand Testbed -> src -> (default package). Right click <code>Test1.java</code> and choose Run as -> Emulated J2ME Midlet.
			[[Link title]]