Difference between revisions of "IoTGateway/BSP/Linux/Quark/FAQ"
From ESS-WIKI
(→application) |
(→application) |
||
| Line 19: | Line 19: | ||
==application== | ==application== | ||
For examples, the following steps will demonstrate how to build static busybox... | For examples, the following steps will demonstrate how to build static busybox... | ||
| − | + | * Install cross tool chain | |
| − | ## [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#To_build_toolchain_installer|To build toolchain installer]] | + | # [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#To_build_all_image_files|To build all image files]] |
| − | + | # [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#To_build_toolchain_installer|To build toolchain installer]] | |
| − | + | # [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#Setting_up_SDK|Setting up SDK]] | |
| + | # [[IoTGateway/BSP/Linux/Quark/Yocto_LBV2_User_Guide#Setting_up_cross_compiling_environment|Setting up cross compiling environment]] | ||
| + | * Install static linked libraries for cross compiling | ||
| + | : (Because there is no static linked library contained in cross toolchain installer.) | ||
| + | : <tt>$ pushd <span style="color:purple">'''${BSP_HOME}'''</span>/<span style="color:purple">'''${BDIR}'''</span>/tmp/sysroots/quark && tar zcvf ~/static_lib.tgz `find ./ -name "*.a"` && popd</tt> | ||
| + | : Copy ~/static_lib.tgz from docker container to home directory in local file system if needed | ||
| + | : <tt>sudo tar xvf ~/static_lib.tgz -C /opt/iot-devkit/<span style="color:purple">'''${POKY}'''</span>/sysroots/i586-poky-linux --no-same-owner</tt> | ||
| + | * Unpack busybox tarball | ||
| + | : <tt>$ mkdir -p ~/code/test_quark</tt> | ||
| + | : <tt>$ tar xvf busybox-1.22.1.tar.bz2 -C ~/code/test_quark</tt> | ||
| + | : <tt>$ cd ~/code/test_quark/busybox-1.22.1</tt> | ||
| + | * Select the option, <tt>"Busybox Settings ---> Build Options---> <b>[*] Build BusyBox as a static binary (no shared libs)</b>"</tt> | ||
| + | : <tt>$ make menuconfig</tt> | ||
| + | : Exit and Save | ||
| + | * do compiling | ||
| + | : <tt>$ make</tt> | ||
| + | * Eventually, the two files, busybox and busybox_unstripped, are exist in directory <tt>"~/code/test_quark/busybox-1.22.1"</tt>. | ||
<br> | <br> | ||
Revision as of 10:03, 12 July 2016
Quark - Frequently Asked Questions
compiling
GRUB
Please refer to the following sections for details
- Getting Started / Build Instructions / To build grub individually (LBV2)
kernel
Please refer to the following sections for details
- Getting Started / Build Instructions / To build linux kernel individually (LBV2)
application
For examples, the following steps will demonstrate how to build static busybox...
- Install cross tool chain
- To build all image files
- To build toolchain installer
- Setting up SDK
- Setting up cross compiling environment
- Install static linked libraries for cross compiling
- (Because there is no static linked library contained in cross toolchain installer.)
- $ pushd ${BSP_HOME}/${BDIR}/tmp/sysroots/quark && tar zcvf ~/static_lib.tgz `find ./ -name "*.a"` && popd
- Copy ~/static_lib.tgz from docker container to home directory in local file system if needed
- sudo tar xvf ~/static_lib.tgz -C /opt/iot-devkit/${POKY}/sysroots/i586-poky-linux --no-same-owner
- Unpack busybox tarball
- $ mkdir -p ~/code/test_quark
- $ tar xvf busybox-1.22.1.tar.bz2 -C ~/code/test_quark
- $ cd ~/code/test_quark/busybox-1.22.1
- Select the option, "Busybox Settings ---> Build Options---> [*] Build BusyBox as a static binary (no shared libs)"
- $ make menuconfig
- Exit and Save
- do compiling
- $ make
- Eventually, the two files, busybox and busybox_unstripped, are exist in directory "~/code/test_quark/busybox-1.22.1".
SDcard image
To build from prebuilt image, please refer to the following sections for details.
- Getting Started / Introducing BSP / Prebuilt image (LBV2)
To build from BSP, please refer to the following sections for details.
- Getting Started / Build Instructions / To build all image files (LBV2)
mini-PCIe
UART