> For the complete documentation index, see [llms.txt](https://theiotlearninginitiative.gitbook.io/ostro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://theiotlearninginitiative.gitbook.io/ostro/build-system/building.md). # Building > The ostro-os repository is a combination of several different components in a single repository. It contains everything that is needed to build Ostro OS. [Github Ostro OS](https://github.com/ostroproject/ostro-os) ## Base Images > ostro-image > > > The default image. Contains all programming runtimes > > ostro-image-dev > > > The same as ostro-image, plus build and debugging tools > > ostro-image-minimal > > > A smaller image which still has the core OS, but none of the optional runtimes ## Intel Edison ```bash xe1gyq@jessie:~/$ git clone https://github.com/ostroproject/ostro-os.git Cloning into 'ostro-os'... remote: Counting objects: 391671, done. remote: Compressing objects: 100% (3054/3054), done. remote: Total 391671 (delta 2035), reused 329 (delta 329), pack-reused 388238 Receiving objects: 100% (391671/391671), 144.42 MiB | 205.00 KiB/s, done. Resolving deltas: 100% (253541/253541), done. Checking connectivity... done. Checking out files: 100% (9520/9520), done. ``` ```bash xe1gyq@jessie:~/$ cd ostro-os/ xe1gyq@jessie:~/ostro-os$ source oe-init-build-env You had no conf/local.conf file. This configuration file has therefore been created for you with some default values. You may wish to edit it to, for example, select a different MACHINE (target hardware). See conf/local.conf for more information as common configuration options are commented. You had no conf/bblayers.conf file. This configuration file has therefore been created for you with some default values. To add additional metadata layers into your configuration please add entries to conf/bblayers.conf. The Yocto Project has extensive documentation about OE including a reference manual which can be found at: http://yoctoproject.org/documentation For more information about OpenEmbedded see their website: http://www.openembedded.org/ ### Shell environment set up for builds. ### You can now run 'bitbake ' Common targets are: ostro-image ostro-image-dev core-image-minimal meta-toolchain adt-installer meta-ide-support Common targets are: ostro-image-noswupd (when building without swupd, the recommended mode for local image building) ostro-image-swupd (when building with swupd, the recommended mode for deployment) We recommend to use VirtualBox if you wish to run an Ostro image in a virtual environment. Please check the doc/howtos/booting-and-installation.rst technical note for more information. ``` ```bash xe1gyq@jessie:~/ostro-os/build$ ls conf xe1gyq@jessie:~/ostro-os/build$ nano conf/local.conf ``` ```bash ... # # Machine Selection # # You need to select a specific machine to target the build with. There are a selection # of several hardware platforms that are supported: # # For MinnowBoard and Gigabyte GB-BXBT-3825: #MACHINE ?= "intel-corei7-64" # # For Intel Galileo Gen 2: #MACHINE ?= "intel-quark" # # For Intel Edison: MACHINE ?= "edison" # # For BeagleBone Black: #MACHINE ?= "beaglebone" # # This sets the default machine to be "intel-corei7-64" if no other machine is selected: MACHINE ??= "intel-corei7-64" ... #PACKAGECONFIG_append_pn-qemu-native = " sdl" #PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" #ASSUME_PROVIDED += "libsdl-native" ... ``` ```bash .... # An explicit choice must be made between building Ostro OS # development images and production images. See # doc/howtows/building-images.rst for further instructions. # Ostro OS development images get built when uncommenting the # following line. Do not do this in production! The resulting images # are not secure. # require conf/distro/include/ostro-os-development.inc # When building production images, configure IMA signing # as described in meta-integrity/README.md if IMA is enabled # and uncomment the following line. # #require conf/distro/include/ostro-os-production.inc ... ``` ```bash xe1gyq@jessie:~/ostro-os/build$ bitbake -k ostro-image-noswupd NOTE: /home/xe1gyq/ostro-os/meta-java/recipes-core/openjdk/openjre-8_72b05.bb: base_contains is deprecated, please use bb.utils.contains instead. NOTE: /home/xe1gyq/ostro-os/meta-java/recipes-core/openjdk/openjdk-8_72b05.bb: base_contains is deprecated, please use bb.utils.contains instead. NOTE: /home/xe1gyq/ostro-os/meta-java/recipes-core/openjdk/openjdk-8-native_72b05.bb: base_contains is deprecated, please use bb.utils.contains instead. NOTE: /home/xe1gyq/ostro-os/meta-java/recipes-core/icedtea/icedtea7-native_2.1.3.bb: base_contains is deprecated, please use bb.utils.contains instead. NOTE: /home/xe1gyq/ostro-os/meta-java/recipes-core/icedtea/icedtea7-native_2.1.3.bb: base_contains is deprecated, please use bb.utils.contains instead. ... Parsing recipes: 19% |############ | ETA: 00:06:32 ... Build Configuration: BB_VERSION = "1.31.0" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "Debian-8.3" TARGET_SYS = "i686-ostro-linux" MACHINE = "edison" DISTRO = "ostro" DISTRO_VERSION = "1.0+snapshot-20160605" TUNE_FEATURES = "m32 edison" TARGET_FPU = "" meta-ostro-fixes meta meta-selftest meta-intel meta-ostro meta-oic meta-security-smack meta-security-framework meta-integrity meta-intel-iot-middleware meta-ostro-bsp meta-edison-bsp meta-iot-web meta-yocto-bsp meta-iotqa meta-appfw meta-security-isafw meta-swupd meta-gnome meta-networking meta-oe meta-python meta-java meta-soletta = "master:13d93e44844452112bf3653537e10007eecf4865" ... NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.1/i686-nativesdk-libc.tar.bz2;sha256sum=1973aa8d07ba4fdae197ea3ffba1274c57ff7923679c364ec8e2b66c73483234 NOTE: Preparing RunQueue NOTE: Checking sstate mirror object availability (for 1020 objects) NOTE: Executing SetScene Tasks Currently 2 running tasks (68 of 1030): 0: linux-firmware-1_144.0+gitAUTOINC+80d463be82-r0 do_populate_sysroot_setscene (pid 21300) 1: linux-firmware-1_144.0+gitAUTOINC+80d463be82-r0 do_package_write_ipk_setscene (pid 22299) ... Currently 2 running tasks (706 of 1030): 0: glibc-locale-2.24-r0 do_package_write_ipk_setscene (pid 3247) 1: u-boot-fw-utils-edison-2014.04-1-r0 do_packagedata_setscene (pid 27968) ... NOTE: Executing RunQueue Tasks Currently 1 running tasks (2722 of 2805): 0: linux-yocto-edison-3.10.98+gitAUTOINC+2e4ace5b68-r0 do_kernel_checkout (pid 21120) ... ``` After 12 hours ... ```bash ... meta-soletta = "master:13d93e44844452112bf3653537e10007eecf4865" NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.1/i686-nativesdk-libc.tar.bz2;sha256sum=1973aa8d07ba4fdae197ea3ffba1274c57ff7923679c364ec8e2b66c73483234 NOTE: Preparing RunQueue NOTE: Checking sstate mirror object availability (for 1020 objects) NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: ostro-image-noswupd-1.0-r0 do_rootfs: The license listed Intel-OBL-Binary-Firmware-License was not in the licenses collected for recipe mcu-fw-bin WARNING: ostro-image-noswupd-1.0-r0 do_rootfs: The license listed Intel-OBL-Binary-Firmware-License was not in the licenses collected for recipe mcu-fw-load WARNING: ostro-image-noswupd-1.0-r0 do_rootfs: [log_check] ostro-image-noswupd: found 2 warning messages in the logfile: [log_check] WARNING: The license listed Intel-OBL-Binary-Firmware-License was not in the licenses collected for recipe mcu-fw-bin [log_check] WARNING: The license listed Intel-OBL-Binary-Firmware-License was not in the licenses collected for recipe mcu-fw-load NOTE: Tasks Summary: Attempted 2805 tasks of which 1782 didn't need to be rerun and all succeeded. Summary: There were 3 WARNING messages shown. xe1gyq@jessie:~/ostro-os/build$ ``` ```bash xe1gyq@jessie:~/ostro-os$ ls bitbake meta-appfw meta-java meta-security-isafw oe-init-build-env build meta-intel meta-oic meta-selftest oe-init-build-env-memres conf meta-intel-iot-middleware meta-openembedded meta-skeleton README.rst doc meta-intel-iot-security meta-ostro meta-soletta scripts LICENSE meta-iotqa meta-ostro-bsp meta-swupd meta meta-iot-web meta-ostro-fixes meta-yocto ``` ```bash xe1gyq@jessie:~/ostro-os/build$ ls tmp-glibc/deploy/images/edison/ bzImage bzImage--3.10.98+git0+2e4ace5b68-r0-edison-20160605054055.bin bzImage-edison.bin flashall ifwi modules--3.10.98+git0+2e4ace5b68-r0-edison-20160605054055.tgz modules-edison.tgz ostro-image-noswupd-edison-20160605054055.hddimg ostro-image-noswupd-edison-20160605054055.rootfs.ext4 ostro-image-noswupd-edison-20160605054055.rootfs.manifest ostro-image-noswupd-edison-20160605054055.rootfs.tar ostro-image-noswupd-edison-20160605054055.rootfs.tar.bz2 ostro-image-noswupd-edison-20160605054055.toflash.tar.bz2 ostro-image-noswupd-edison-20160605054055.update.hddimg ostro-image-noswupd-edison-20160605054055.update.tar.gz ostro-image-noswupd-edison.ext4 ostro-image-noswupd-edison.hddimg ostro-image-noswupd-edison.manifest ostro-image-noswupd-edison.tar ostro-image-noswupd-edison.tar.bz2 ostro-image-noswupd-edison.toflash.tar.bz2 ostro-image-noswupd-edison.update.hddimg ostro-image-noswupd-edison.update.tar.gz README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt u-boot.bin u-boot-edison-2014.04-1-r6.bin u-boot-edison-2014.04-1-r6.img u-boot-edison.bin u-boot-edison.img u-boot-envs u-boot.img xe1gyq@jessie:~/ostro-os/build$ ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://theiotlearninginitiative.gitbook.io/ostro/build-system/building.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.