BRN:Software:Build and Distribution:SDE - Revision history

Jeschke at 13:49, 8 September 2006

2006-09-08T13:49:41Z

← Older revision		Revision as of 13:49, 8 September 2006
Line 40:		Line 40:

	----		----
	[[BRN:Software:Build_and_Distribution:Compiler\|Prev]] \| [[BRN:Software:Build_and_Distribution\|Contents]] \| [[BRN:Software:Build_and_Distribution:Linux\|Next]]		<span style="padding-left:0.5em">'''[[BRN:Software:Build_and_Distribution:Compiler\|Prev]]''' \| '''[[BRN:Software:Build_and_Distribution\|Contents]]''' \| '''[[BRN:Software:Build_and_Distribution:Linux\|Next]]'''</span>

Jeschke: /* FS Image */

2006-09-08T09:00:54Z

FS Image

← Older revision		Revision as of 09:00, 8 September 2006
Line 21:		Line 21:
	I suggest to use cramfs. Cramfs supports encryption and you do not need to create a block device image. Additionally the contents of this image become read-only status later and protected against modifications.		I suggest to use cramfs. Cramfs supports encryption and you do not need to create a block device image. Additionally the contents of this image become read-only status later and protected against modifications.

			=== Creation ===
	Create the directory structure:		Create the directory structure:

	$ mkdir -p toolchain/openwgt-dev/buildroot/build_mipsel		$ mkdir -p toolchain/openwgt-dev/buildroot/build_mipsel

	Move your ''staging_dir'' directory:		Move your ''staging_dir'' directory:

	$ mv openwgt-dev/buildroot/build_mipsel/staging_dir toolchain/openwgt-dev/buildroot/build_mipsel		$ mv openwgt-dev/buildroot/build_mipsel/staging_dir toolchain/openwgt-dev/buildroot/build_mipsel

	Finally create the cramfs image (util-linux package):		Finally create the cramfs image (util-linux package):
		⚫	$ /sbin/mkfs.cramfs -E toolchain sde-wgt-toolchain.cramfs

			=== Usage ===
⚫	$ /sbin/mkfs.cramfs -E toolchain sde-wgt-toolchain.cramfs
			Make mount point:
			$ mkdir /sde-wgt-toolchain

			Mount the image:
			$ mount -o loop,ro sde-wgt-toolchain.cramfs /sde-wgt-toolchain

	'''TODO'''
	-> Mount-Hinweise

	----		----

Jeschke: /* Tarball */

2006-09-08T08:58:18Z

Tarball

← Older revision		Revision as of 08:58, 8 September 2006
Line 5:		Line 5:

	== Tarball ==		== Tarball ==
			=== Creation ===
	To create a tarball with all binaries and include files, run:		To create a tarball with all binaries and include files, run:
	$ tar czf sde-wgt-toolchain.tar.gz openwgt-dev/buildroot/build_mipsel/staging_dir		$ tar czf sde-wgt-toolchain.tar.gz openwgt-dev/buildroot/build_mipsel/staging_dir
Line 10:		Line 11:
	The tarball will created as '''sde-wgt-toolchain.tar.gz'''.		The tarball will created as '''sde-wgt-toolchain.tar.gz'''.

			=== Usage ===
	To extract it, run:		To extract it, run:
	$ TOOLCHAIN_PATH=/sde-wgt-toolchain # or any other location, you prefer		$ TOOLCHAIN_PATH=/sde-wgt-toolchain # or any other location, you prefer

Jeschke: /* FS Image */

2006-09-07T14:55:12Z

FS Image

← Older revision		Revision as of 14:55, 7 September 2006
Line 16:		Line 16:

	== FS Image ==		== FS Image ==
			If you choose this option you have to select a filesystem, that will contain your toolchain later.
			I suggest to use cramfs. Cramfs supports encryption and you do not need to create a block device image. Additionally the contents of this image become read-only status later and protected against modifications.

			Create the directory structure:

			$ mkdir -p toolchain/openwgt-dev/buildroot/build_mipsel

			Move your ''staging_dir'' directory:

			$ mv openwgt-dev/buildroot/build_mipsel/staging_dir toolchain/openwgt-dev/buildroot/build_mipsel

			Finally create the cramfs image (util-linux package):

			$ /sbin/mkfs.cramfs -E toolchain sde-wgt-toolchain.cramfs

			'''TODO'''
			-> Mount-Hinweise

	----		----

Jeschke at 14:37, 7 September 2006

2006-09-07T14:37:16Z

← Older revision		Revision as of 14:37, 7 September 2006
Line 1:		Line 1:
	If you have built your toolchain, it may be nice to reuse the same toolchain on other machines or ~~shared~~ it with other developers.		If you have built your toolchain, it may be nice to reuse the same toolchain on other machines or to share it with other developers.

	= Creating a Standard Development Environemnt =		= Creating a Standard Development Environemnt =

Jeschke at 14:36, 7 September 2006

2006-09-07T14:36:49Z

← Older revision		Revision as of 14:36, 7 September 2006
Line 1:		Line 1:
	If you have built your toolchain, it may be ~~useful~~ to ~~use~~ the same toolchain on other machines or shared it with other developers.		If you have built your toolchain, it may be nice to reuse the same toolchain on other machines or shared it with other developers.

	= Creating a Standard Development Environemnt =		= Creating a Standard Development Environemnt =

Jeschke: /* Added footer */

2006-09-07T14:33:59Z

Added footer

← Older revision		Revision as of 14:33, 7 September 2006
Line 16:		Line 16:

	== FS Image ==		== FS Image ==



			----
			[[BRN:Software:Build_and_Distribution:Compiler\|Prev]] \| [[BRN:Software:Build_and_Distribution\|Contents]] \| [[BRN:Software:Build_and_Distribution:Linux\|Next]]

Jeschke at 14:29, 7 September 2006

2006-09-07T14:29:40Z

← Older revision		Revision as of 14:29, 7 September 2006
Line 2:		Line 2:

	= Creating a Standard Development Environemnt =		= Creating a Standard Development Environemnt =
	To ~~reallise~~ this, create a container for the directory buildroot and copy the necessary files into it. You can choose between a tarball or filesystem image, which can be loop mounted into your running Linux development machine.		To realise this, create a container for the directory buildroot and copy the necessary files into it. You can choose between a tarball or filesystem image, which can be loop mounted into your running Linux development machine.

	== Tarball ==		== Tarball ==

Jeschke: /* Tarball */

2006-09-07T14:28:10Z

Tarball

← Older revision		Revision as of 14:28, 7 September 2006
Line 5:		Line 5:

	== Tarball ==		== Tarball ==
			To create a tarball with all binaries and include files, run:
			$ tar czf sde-wgt-toolchain.tar.gz openwgt-dev/buildroot/build_mipsel/staging_dir

			The tarball will created as '''sde-wgt-toolchain.tar.gz'''.

			To extract it, run:
			$ TOOLCHAIN_PATH=/sde-wgt-toolchain # or any other location, you prefer
			$ mkdir -p $TOOLCHAIN_PATH
			$ tar xzf sde-wgt-toolchain.tar.gz -C $TOOLCHAIN_PATH --no-same-owner

	== FS Image ==		== FS Image ==

Jeschke at 13:55, 7 September 2006

2006-09-07T13:55:25Z

New page

If you have built your toolchain, it may be useful to use the same toolchain on other machines or shared it with other developers.

= Creating a Standard Development Environemnt =
To reallise this, create a container for the directory buildroot and copy the necessary files into it. You can choose between a tarball or filesystem image, which can be loop mounted into your running Linux development machine.

== Tarball ==

== FS Image ==