To generate PKG_MIRROR_HASH automatically, use the following (replace package/network/services/odhcpd by your package): The tarballs generated from svn checkouts are not reproducible, so you should avoid defining PKG_MIRROR_HASH when building from svn!
ELINKS SET CUSTOM HEADER DOWNLOAD
This way, users building OpenWrt will directly download the generated tarball from a buildbot and verify its checksum, thus avoiding a clone of the source repository. You should also define PKG_MIRROR_HASH with the SHA256 checksum of this generated tarball. a commit hash for git, or a revision number for svn)īuildroot will first clone the source repository, and then generate a tarball from the source repository, with a name like dl/. PKG_SOURCE_PROTO supports download from various repositories to integrate development versions:īesides the source repository PKG_SOURCE_ URL, you also need to specify which exact version you are building using PKG_SOURCE_VERSION (e.g. This is a way of providing a level of verbosity, it's inherently clear what the DESCRIPTION variable in Package/bridge is, which wouldn't be the case if we passed this information directly as the Nth argument to BuildPackage.Īvoid reuse of PKG_NAME in call, define and eval lines for consistency and readability. All other information is taken from the define blocks.
BuildPackage only takes one argument directly - the name of the package to be built, in this case “bridge”.
ELINKS SET CUSTOM HEADER INSTALL
PKG_INSTALL_DIR defines where the files will be copied after calling “make install” (set with the PKG_INSTALL variable), and after that you can package them in the install section.Īt the bottom of the file is where the real magic happens, “BuildPackage” is a macro setup by the earlier include statements. The md5sum is used to verify the package was downloaded correctly and PKG_BUILD_DIR defines where to find the package after the sources are uncompressed into $(BUILD_DIR). The PKG_* variables define where to download the package from is a special keyword for downloading packages from sourceforge. PKG_SOURCE_SUBDIR - where the temporary source checkout should be stored, defaults to $(PKG_NAME)-$(PKG_VERSION) $ ( eval $ ( call BuildPackage ,bridge ) ) BuildPackage variables $ ( INSTALL_BIN ) $ ( PKG_BUILD_DIR ) /brctl /brctl $ ( 1 ) /usr /sbin / $ ( call Build /Configure /Default ,-with -linux -headers =$ ( LINUX_DIR ) ) Manage ethernet bridging a way to connect networks together to use the Package/name/description define instead! TITLE :=Ethernet bridging configuration utility PKG_SOURCE :=bridge -utils -$ ( PKG_VERSION ). PKG_BUILD_DIR :=$ ( BUILD_DIR ) /bridge -utils -$ ( PKG_VERSION ) Here, for example, is package/bridge/Makefile: Through what can only be described as blatant disregard and abuse of the traditional make format, the Makefile has been transformed into an object oriented template which simplifies the entire ordeal.
Looking at one of the package makefiles, you'd hardly recognize it as a makefile. The package Makefile is the important item because it provides the steps actually needed to download and compile the package. It typically includes default config or init files.
The patches directory is optional and typically contains bug fixes or optimizations to reduce the size of the executable.
0 kommentar(er)
