![]() ![]() Remarkably, all that needs to be done to add a new profile, is to add a new file to the profiles directory. The location of the profiles for the pre-compiled package for brcm47xx-for-Linux-i686 was target/linux/brcm47xx/profiles/ Remove the /tmp directory to properly apply the modified package selection from profiles. If you add a new profile without also adding an appropriate macro to the image-generation Makefile, no suitable firmware file will get generated when using the custom profile. The image building is tied to the profile names. They are very low level so expect to have a good level of skill and familiarity with the ImageBuilder / OpenWrt in general. NOTE: if you want to override packages coming from an existing feed, you must write your custom feed ABOVE the line of the package feed containing the packages you want to override, as shown in the examples above.Įxamples below may contain version dependent / legacy information and are for informational purposes. If you have custom repositories online, copy and modify the src/gz reboot line instead. If you have problems with using you local repository because the “Signature check failed” then remove the line option check_signature from nf If you want to add a custom local repository, copy the src custom file:///usr/src/openwrt/bin/ramips/packages line and modify it to point to the local folder where you have your packages and package lists ( example package list). The nf in an imagebuilder you compile from source will lack the “Remote package repositories” links. # This is the local package repository, do not remove! Src /gz openwrt_telephony http: // /releases /18.06.0-rc2 /packages /mipsel_24kc /telephony Src /gz openwrt_routing http: // /releases /18.06.0-rc2 /packages /mipsel_24kc /routing ![]() Src /gz openwrt_packages http: // /releases /18.06.0-rc2 /packages /mipsel_24kc /packages Src /gz openwrt_luci http: // /releases /18.06.0-rc2 /packages /mipsel_24kc /luci Src /gz openwrt_base http: // /releases /18.06.0-rc2 /packages /mipsel_24kc /base Src /gz openwrt_core http: // /releases /18.06.0-rc2 /targets /ramips /mt7621 /packages # src/gz %n # src custom file:///usr/src/openwrt/bin/ramips/packages # Remote package repositories # Place your custom repositories here, they must match the architecture and version. This can be either the official package repositories or custom generated repositories.Īn example of the contents of the nf from the openwrt-imagebuilder-18.06.0-rc2-ramips-mt7621.Linux-x86_64.tar.xz: Sources are specified in opkg native config format. The package sources are configured in the nf file in the extracted directory. The Image Builder you download from the OpenWrt pages is already configured to download any non-default packages from official repositories. Make manifest STRIP_ABI=1 # remove ABI version from printed package names Available profiles Make manifest PACKAGES=" ]" # include extra packages Make manifest PROFILE="" # override the default target profile List "all" packages which get installed into the image. Make image ADD_LOCAL_KEY=1 # store locally generated signing key in built images Make image DISABLED_SERVICES=" ]" # Which services in /etc/init.d/ should be disabled Make image EXTRA_IMAGE_NAME="" # Add this to the output image filename (sanitized) Make image BIN_DIR="" # alternative output directory for the images ![]() Make image FILES="" # include extra files from Make image PACKAGES=" ]" # include extra packages Make image PROFILE="" # override the default target profile ![]() Image:ěuild an image (see below for more information).īy default 'make image' will create an image with the default Info: Show a list of available target profilesĬlean: Remove images and temporary build files ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |