User:DenisB - Revision history

DenisB: /* Misc 1 : Qemu launching */ script works undder FC17 and armadeus5.0, too

2012-09-02T14:19:09Z

Misc 1 : Qemu launching: script works undder FC17 and armadeus5.0, too

← Older revision		Revision as of 16:19, 2 September 2012
Line 96:		Line 96:

	Nota : this script has been tested and run with some satisfaction for more than one month on Scientific Linux - 5.7 (a Red Hat clone, able to mount NTFS partitions and having a live DVD),Fedora 16 and a Mageia-1: emulated cards were apf9328 and apf27.		Nota : this script has been tested and run with some satisfaction for more than one month on Scientific Linux - 5.7 (a Red Hat clone, able to mount NTFS partitions and having a live DVD),Fedora 16 and a Mageia-1: emulated cards were apf9328 and apf27.
			(it is also used with Armadeus-5.0, under Fedora 17)
	The only flaw I could notice with SL-5.x was the absence of qemu on their live DVD (it is difficult to have a package manager add stuff on a RO media...) , which could be recompiled from source in a RW part of a disk with little trouble.		The only flaw I could notice with SL-5.x was the absence of qemu on their live DVD (it is difficult to have a package manager add stuff on a RO media...) , which could be recompiled from source in a RW part of a disk with little trouble.

DenisB: /* Misc 2 */ typos

2012-01-19T10:18:53Z

Misc 2: typos

← Older revision		Revision as of 12:18, 19 January 2012
Line 136:		Line 136:
	arm-linux-strip joe		arm-linux-strip joe
	ls -l joe >> joestrip.txt		ls -l joe >> joestrip.txt
	# puts joe into armadeus files ~~ans prepears~~ installation		# puts joe into armadeus files and prepares installation
	#		#
	cp joe ../tftboot/. # it is ready to be ~~shiped~~ to an emulated card..		cp joe ../tftboot/. # it is ready to be shipped to an emulated card..
	mkdir .././tftboot/usrlocalshare		mkdir .././tftboot/usrlocalshare
	cp -rpvf ${JOERROT}/share/joe .././tftboot/usrlocalshare/.		cp -rpvf ${JOERROT}/share/joe .././tftboot/usrlocalshare/.

DenisB: /* Misc 2 */

2012-01-10T16:10:53Z

Misc 2

← Older revision		Revision as of 18:10, 10 January 2012
Line 106:		Line 106:

	Natively, armadeus is shipped with nano, a very simple version of vi (not like vim) and uemacs. If one needs some features like syntax highlighting (for shell/lua scripting) , noone of them is satisfying (and a full version of vim can be installed, but is space-consuming).		Natively, armadeus is shipped with nano, a very simple version of vi (not like vim) and uemacs. If one needs some features like syntax highlighting (for shell/lua scripting) , noone of them is satisfying (and a full version of vim can be installed, but is space-consuming).
	A light solution can be found with joe [http://joe-editor.sourceforge.net/], which offers syntax-highlighting (I noticed that 10% of my errors could be avoided with such a feature).		A light solution can be found with joe [http://joe-editor.sourceforge.net/], which offers in-line help and syntax-highlighting (I noticed that 10% of my errors could be avoided with such a feature).
	The easiest solution is to compile it from source, test it and train oneself with it, and to modify the make invocation to use Armadeus's cross compiler instead of gcc, which leads to the following script one should execute on ~~ones~~ PC:		The easiest solution is to compile it from source for one's PC, test it and train oneself with it, and to modify the make invocation to use Armadeus's cross compiler instead of gcc, which leads to the following script one should execute on one's PC:

	<source lang="bash">		<source lang="bash">
	JOEROOT=/usr/local/ # in both the PC and the (emulated) Armadeus card tomake things simple....		JOEROOT=/usr/local/ # in both the PC and the (emulated) Armadeus card tomake things simple....

	cd /usr/local/armadeus-4.0/# ~~both~~ these lines depend on your installation and should be adapted		cd /usr/local/armadeus-4.0/# these 3 lines depend on your installation and should obviously be adapted
	cd ~/armadeus-4.0/		cd ~/armadeus-4.0/
	cd joe-3.7/ # joe's source tree is located here		cd joe-3.7/ # joe's source tree is located here
Line 128:		Line 128:
	# one removes x86 binaries, then one builds for arm		# one removes x86 binaries, then one builds for arm
	make clean && make CC=arm-linux-gcc		make clean && make CC=arm-linux-gcc
	# some tests		# some tests (mainly of strip)

	echo "unstripped joe " > joestrip.txt		echo "unstripped joe " > joestrip.txt
Line 136:		Line 136:
	arm-linux-strip joe		arm-linux-strip joe
	ls -l joe >> joestrip.txt		ls -l joe >> joestrip.txt
			# puts joe into armadeus files ans prepears installation
			#
	cp joe ../tftboot/. # it is ready to be shiped to an emulated card..		cp joe ../tftboot/. # it is ready to be shiped to an emulated card..
	mkdir .././tftboot/usrlocalshare		mkdir .././tftboot/usrlocalshare
Line 145:		Line 146:
	</source>		</source>

	In this configuration, joe can be activated from an emulated card, its help appears but there is no syntax highligting. The ressource files/folders necessary to syntax highlight , however, have been shipped (they are ASCII files, valid on a x86 and an arm) but need to be on the right place. This can be ~~achievd~~ by executing, under an emulated board, a script like that:		In this configuration, joe can be activated from an emulated card, its help appears but there is no syntax highligting (it was meant for!) . The ressource files/folders necessary to syntax highlight , however, have been shipped (they are ASCII files, valid on a x86 and an arm) but need to be on the right place. This can be achieved by executing, under an emulated board, a script like that:

	<source lang=bash>		<source lang=bash>

DenisB: /* Misc 1 : Qemu launching */

2012-01-10T16:05:02Z

Misc 1 : Qemu launching

← Older revision		Revision as of 18:05, 10 January 2012
Line 3:		Line 3:
	'''1) A script to make qemu launching automatic'''		'''1) A script to make qemu launching automatic'''

	Sometimes, the list of commands one has to type as host can be very long and tedious; and forgetting to type one of them ~~leads~~ to unpleasant results (ex : a mounted image should be unmounted before being used by qemu)		Sometimes, the list of commands one has to type as host can be very long and tedious; and forgetting to type one of them might lead to unpleasant results (ex : a mounted image should be unmounted before being used by qemu)

	a bash script like this one, once adapted, might give ideas to avoid errors..		a bash script like this one, once adapted, might give ideas to avoid errors and typos..

	<source lang="bash">		<source lang="bash">

DenisB: /* Misc 2 */ Added a picture of joe'editor at work

2012-01-09T15:57:00Z

Misc 2: Added a picture of joe'editor at work

← Older revision		Revision as of 17:57, 9 January 2012
Line 154:		Line 154:
	</source>		</source>

	After this installation (there are better ones, based on tar files, say: - tar exists with Busy ~~Box_~~ but this way can give opportunities of easily removing some syntax files, if they are felt unuseful), syntax highlight works...		After this installation (there are better ones, based on tar files, say: - a simple tar exists with Busy Box or a full version can be installed- but this way can give opportunities of easily removing some syntax files, if they are felt unuseful), syntax highlight works...

	One can seen a screenshot here (joe is launched from a qemu-lated armadeus, the host system being a Fedora Core 16, with KDE as desktop manager):		One can seen a screenshot here (joe is launched from a qemu-lated armadeus, the host system being a Fedora Core 16, with KDE as desktop manager):
	[[image:snapshot_qemu_joe1.png\|center\|frame\|thumb\|'''figure 1''' - ''a session with Joe's editor'']]		[[image:snapshot_qemu_joe1.png\|center\|frame\|thumb\|'''figure 1''' - ''a session with Joe's editor'']]

DenisB: /* Misc 2 */

2012-01-09T15:55:00Z

Misc 2

← Older revision		Revision as of 17:55, 9 January 2012
Line 154:		Line 154:
	</source>		</source>

	After this installation (there are better ones, based on tar files, say: as tar exists with Busy ~~Box,~~ but this way can give opportunities of easily removing some syntax files, if they are felt unuseful), syntax highlight works...		After this installation (there are better ones, based on tar files, say: - tar exists with Busy Box_ but this way can give opportunities of easily removing some syntax files, if they are felt unuseful), syntax highlight works...
			One can seen a screenshot here (joe is launched from a qemu-lated armadeus, the host system being a Fedora Core 16, with KDE as desktop manager):
			[[image:snapshot_qemu_joe1.png\|center\|frame\|thumb\|'''figure 1''' - ''a session with Joe's editor'']]

DenisB: /* Misc 2 */

2011-12-02T14:47:17Z

Misc 2

← Older revision		Revision as of 16:47, 2 December 2011
Line 150:		Line 150:
	[ -d /usr/local/share ] \|\| mkdir /usr/local/share		[ -d /usr/local/share ] \|\| mkdir /usr/local/share
	[ -d /usr/local/etc ] \|\| mkdir /usr/local/etc		[ -d /usr/local/etc ] \|\| mkdir /usr/local/etc
	mv /usr/local/bin/usrlocalshare/joe /usr/local/share/.		\mv /usr/local/bin/usrlocalshare/joe /usr/local/share/.
	\mv /usr/local/bin/~~usrlocalshare~~/joe /usr/local/~~share~~/.		\mv /usr/local/bin/usrlocaletc/joe /usr/local/etc/.
	</source>		</source>

	After this installation (there are better ones, based on tar files, say: as tar exists ~~wth the busy box~~, but this way can give opportunities of removing ~~language~~ syntax files, if they are unuseful), syntax highlight works...		After this installation (there are better ones, based on tar files, say: as tar exists with Busy Box, but this way can give opportunities of easily removing some syntax files, if they are felt unuseful), syntax highlight works...

DenisB: /* Misc 2 */

2011-12-02T10:30:34Z

Misc 2

← Older revision		Revision as of 12:30, 2 December 2011
Line 154:		Line 154:
	</source>		</source>

	After this installation (there are better ones, based on tar files, say as tar exists wth the busy box, but this way can give opportunities of removing language syntax files, if they are unuseful), ~~syntx~~ highlight works...		After this installation (there are better ones, based on tar files, say: as tar exists wth the busy box, but this way can give opportunities of removing language syntax files, if they are unuseful), syntax highlight works...

DenisB: /* Misc 2 */

2011-12-02T10:29:52Z

Misc 2

← Older revision		Revision as of 12:29, 2 December 2011
Line 145:		Line 145:
	</source>		</source>

	In this configuration, joe can be activated from an emulated card, its help appears but there is no syntax highligting. The ressource files/folders necessary to syntax highlight , however, have been shipped (they are ASCII files, valid on a x86 and an arm) but need to be on the right place.		In this configuration, joe can be activated from an emulated card, its help appears but there is no syntax highligting. The ressource files/folders necessary to syntax highlight , however, have been shipped (they are ASCII files, valid on a x86 and an arm) but need to be on the right place. This can be achievd by executing, under an emulated board, a script like that:

			<source lang=bash>
			[ -d /usr/local/share ] \|\| mkdir /usr/local/share
			[ -d /usr/local/etc ] \|\| mkdir /usr/local/etc
			mv /usr/local/bin/usrlocalshare/joe /usr/local/share/.
			\mv /usr/local/bin/usrlocalshare/joe /usr/local/share/.
			</source>

			After this installation (there are better ones, based on tar files, say as tar exists wth the busy box, but this way can give opportunities of removing language syntax files, if they are unuseful), syntx highlight works...

DenisB: /* Misc 2 */

2011-12-01T16:05:54Z

Misc 2

← Older revision		Revision as of 18:05, 1 December 2011
Line 107:		Line 107:
	Natively, armadeus is shipped with nano, a very simple version of vi (not like vim) and uemacs. If one needs some features like syntax highlighting (for shell/lua scripting) , noone of them is satisfying (and a full version of vim can be installed, but is space-consuming).		Natively, armadeus is shipped with nano, a very simple version of vi (not like vim) and uemacs. If one needs some features like syntax highlighting (for shell/lua scripting) , noone of them is satisfying (and a full version of vim can be installed, but is space-consuming).
	A light solution can be found with joe [http://joe-editor.sourceforge.net/], which offers syntax-highlighting (I noticed that 10% of my errors could be avoided with such a feature).		A light solution can be found with joe [http://joe-editor.sourceforge.net/], which offers syntax-highlighting (I noticed that 10% of my errors could be avoided with such a feature).
	The easiest solution is to compile it from source, test it and train oneself with it, and to modify the make invocation to use Armadeus's cross compiler instead of gcc, which leads to the following script:		The easiest solution is to compile it from source, test it and train oneself with it, and to modify the make invocation to use Armadeus's cross compiler instead of gcc, which leads to the following script one should execute on ones PC:

			<source lang="bash">
			JOEROOT=/usr/local/ # in both the PC and the (emulated) Armadeus card tomake things simple....

	~~JOEROOT=/usr/local/ # in both the PC and the (emulated) Armadeus card....~~
	cd /usr/local/armadeus-4.0/# both these lines depend on your installation and should be adapted		cd /usr/local/armadeus-4.0/# both these lines depend on your installation and should be adapted
	cd ~/armadeus-4.0/		cd ~/armadeus-4.0/
	cd joe-3.7/ # joe's source tree is located here		cd joe-3.7/ # joe's source tree is located here

	ici=`pwd`		ici=`pwd`
	make clean # first, removes everything (might be arm's binaries)		make clean # first, removes everything (might be arm's binaries)
Line 140:		Line 143:
	cp -rpvf ${JOERROT}/etc/joe .././tftboot/usrlocaletc/.		cp -rpvf ${JOERROT}/etc/joe .././tftboot/usrlocaletc/.
	# history >joestory		# history >joestory
			</source>

			In this configuration, joe can be activated from an emulated card, its help appears but there is no syntax highligting. The ressource files/folders necessary to syntax highlight , however, have been shipped (they are ASCII files, valid on a x86 and an arm) but need to be on the right place.