User Tools

Site Tools


docs:guide-developer:helloworld:chapter3

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
docs:guide-developer:helloworld:chapter3 [2018/04/16 10:02]
armand2 [Conclusion]
docs:guide-developer:helloworld:chapter3 [2018/06/01 08:36] (current)
tmomas LEDE -> OpenWrt
Line 3: Line 3:
 ====== Creating a package from your application ====== ====== Creating a package from your application ======
  
-This is the third chapter in the "​Hello,​ world!"​ for LEDE article series. At this point, you should'​ve already accomplished the following tasks:+This is the third chapter in the "​Hello,​ world!"​ for OpenWrt ​article series. At this point, you should'​ve already accomplished the following tasks:
   * Commissioned your development environment   * Commissioned your development environment
   * Prepared, configured and built the tools and the cross-compilation toolchain   * Prepared, configured and built the tools and the cross-compilation toolchain
Line 13: Line 13:
 ===== Creating a package feed for your packages ===== ===== Creating a package feed for your packages =====
  
-The LEDE build system revolves heavily around the concept of packages. They are the bread and butter of the system. No matter the software, there'​s almost always a package for it. This applies to nearly everything in the system, be it the target-independent tools, the cross-compilation toolchain, the Linux kernel of the target firmware, the additional modules that are bundled with the kernel or the various applications that will be installed onto the root file system of the target firmware.+The OpenWrt ​build system revolves heavily around the concept of packages. They are the bread and butter of the system. No matter the software, there'​s almost always a package for it. This applies to nearly everything in the system, be it the target-independent tools, the cross-compilation toolchain, the Linux kernel of the target firmware, the additional modules that are bundled with the kernel or the various applications that will be installed onto the root file system of the target firmware.
  
 Due to this package-oriented nature, it is only logical to utilize the same approach for the "​Hello,​ World! -application as well. Due to this package-oriented nature, it is only logical to utilize the same approach for the "​Hello,​ World! -application as well.
Line 27: Line 27:
 ===== Creating the package manifest file ===== ===== Creating the package manifest file =====
  
-Each package in the LEDE build system is described by a package manifest file. The manifest file is responsible for describing the package, what it does, and must at least provide instructions on where to obtain the source code, how to build it and which files should be contained in the final installable package. A package manifest may additionally contain options for optional configuration scripts, specify dependencies between packages and so on.+Each package in the OpenWrt ​build system is described by a package manifest file. The manifest file is responsible for describing the package, what it does, and must at least provide instructions on where to obtain the source code, how to build it and which files should be contained in the final installable package. A package manifest may additionally contain options for optional configuration scripts, specify dependencies between packages and so on.
  
 In order for the source code of our application to become a package, and become a part of the package repository that we previously created, we will need to create a package manifest for it: In order for the source code of our application to become a package, and become a part of the package repository that we previously created, we will need to create a package manifest for it:
docs/guide-developer/helloworld/chapter3.1523872965.txt.gz · Last modified: 2018/04/16 10:02 by armand2