This is the fourth chapter in the “Hello, world!” for OpenWrt article series. At this point, you should've already accomplished the following tasks:
If you missed one or more of these steps, review the previous chapters.
The OpenWrt build system uses a specific file called
feeds.conf which indicates the package feeds that will be made available during the firmware configuration stage. In order for the package containing the application to be made visible in the first place, it is necessary to include the new package feed into this file.
By default, this file does not exist in the OpenWrt source code directory, so it is necessary to create it:
cd /home/buildbot/source touch feeds.conf
Modify the file with the text editor to specify the local package feed:
src-link mypackages /home/buildbot/mypackages
Now that the new feed is defined, we can instruct the build system to update its package index based on the information available in this feed, and to make all packages in this feed available in the configuration menu. This can be achieved by issuing the following commands:
cd /home/buildbot/source ./scripts/feeds update mypackages ./scripts/feeds install -a -p mypackages
Note that whenever you modify the package manifest file, the feeds system will automatically detect this, and will perform an update on your behalf before completing other commands such as 'make menuconfig' or before building a package.
In this chapter, we created a feed configuration file called 'feeds.conf', adding our local package feed into the file. We then updated the package index from this feed and installed all packages available in this feed, ready to be included in the firmware configuration.