BRN:Software:Build and Distribution:SDE: Difference between revisions
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): |
||
⚫ | |||
=== Usage === |
|||
⚫ | |||
Make mount point: |
|||
$ mkdir /sde-wgt-toolchain |
|||
Mount the image: |
|||
$ mount -o loop,ro sde-wgt-toolchain.cramfs /sde-wgt-toolchain |
|||
'''TODO''' |
|||
-> Mount-Hinweise |
|||
---- |
---- |
Revision as of 09:00, 8 September 2006
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
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
Creation
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.
Usage
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
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.
Creation
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
Usage
Make mount point:
$ mkdir /sde-wgt-toolchain
Mount the image:
$ mount -o loop,ro sde-wgt-toolchain.cramfs /sde-wgt-toolchain