BRN:Software:Build and Distribution:SDE: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| 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 == |
||
Revision as of 14:28, 7 September 2006
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
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