aboutsummaryrefslogtreecommitdiffstats
path: root/tools/padjffs2
Commit message (Collapse)AuthorAgeFilesLines
* tools: drop PKG_VERSION for purely local packagesAdrian Schmutzler2020-07-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This applies to tools directory what has been done for package/ in commit 9c170cb92f4f ("package: drop PKG_VERSION for purely local packages"): In the package guidelines, PKG_VERSION is supposed to be used as "The upstream version number that we're downloading", while PKG_RELEASE is referred to as "The version of this package Makefile". Thus, the variables in a strict interpretation provide a clear distinction between "their" (upstream) version in PKG_VERSION and "our" (local OpenWrt trunk) version in PKG_RELEASE. For local (OpenWrt-only) packages, this implies that those will only need PKG_RELEASE defined, while PKG_VERSION does not apply following a strict interpretation. While the majority of "our" packages actually follow that scheme, there are also some that mix both variables or have one of them defined but keep them at "1". This is misleading and confusing, which can be observed by the fact that there typically either one of the variables is never bumped or the choice of the variable to increase depends on the person doing the change. Consequently, this patch aims at clarifying the situation by consistently using only PKG_RELEASE for "our" packages. For tools/, only three packages were affected. This fixes two of them, and leaves the remaining wrt350nv2-builder untouched, as the code there seems to have some versioning of its own that is treated as upstream version in PKG_VERSION. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* tools: padjffs2: add option to output padding data to stdoutYousong Zhou2016-07-111-4/+16
| | | | Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* tools: remove static linking supportJo-Philipp Wich2015-02-061-1/+1
| | | | | | Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 44285
* padjffs2: add a different kind of padding (using standard jffs2 elements) to ↵Felix Fietkau2013-11-141-17/+49
| | | | | | | | work around broken boot loaders for kernel partitions Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 38804
* tools/padjffs2: allow to specify extra offsetGabor Juhos2013-09-251-3/+14
| | | | | | | | | This will be useful for firmware images which are using a custom header. Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 38195
* convert remaining tools to $(HOST_STATIC_LINKING) (#12012)Jo-Philipp Wich2012-08-121-1/+1
| | | | SVN-Revision: 33148
* padjffs2: link staticallyJo-Philipp Wich2012-08-102-2/+6
| | | | SVN-Revision: 33100
* tools: clean up Makefiles / make ccache workJohn Crispin2012-01-151-4/+0
| | | | SVN-Revision: 29754
* padjffs2: fix a compiler warning that makes the build fail because of -WerrorFelix Fietkau2011-07-021-1/+1
| | | | SVN-Revision: 27361
* tools: create a new tool for more efficient jffs2 paddingGabor Juhos2011-07-023-0/+206
SVN-Revision: 27355