Commit Graph

11 Commits

Author SHA1 Message Date
Christian Marangi
aa77c796fe
tools/padjffs2: use Host/Prepare/Default instead of raw commands
Now that Host/Prepare/Default is always defined, we can use that instead
of using raw commands to move files from the src directory to
HOST_BUILD_DIR.

Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
(cherry picked from commit 01048c7456)
2024-05-22 12:00:40 +02:00
Adrian Schmutzler
240793d175 tools: drop PKG_VERSION for purely local packages
This applies to tools directory what has been done for package/ in
commit 9c170cb92f ("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>
2020-07-23 10:54:33 +02:00
Yousong Zhou
d06b68fe83 tools: padjffs2: add option to output padding data to stdout
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
2016-07-11 13:26:33 +02:00
Jo-Philipp Wich
f7e56763e1 tools: remove static linking support
Signed-off-by: Jo-Philipp Wich <jow@openwrt.org>

SVN-Revision: 44285
2015-02-06 00:00:43 +00:00
Felix Fietkau
cc8350c5ec padjffs2: add a different kind of padding (using standard jffs2 elements) to work around broken boot loaders for kernel partitions
Signed-off-by: Felix Fietkau <nbd@openwrt.org>

SVN-Revision: 38804
2013-11-14 19:04:44 +00:00
Gabor Juhos
2bcab84045 tools/padjffs2: allow to specify extra offset
This will be useful for firmware images which are
using a custom header.

Signed-off-by: Gabor Juhos <juhosg@openwrt.org>

SVN-Revision: 38195
2013-09-25 20:03:19 +00:00
Jo-Philipp Wich
7304953292 convert remaining tools to $(HOST_STATIC_LINKING) (#12012)
SVN-Revision: 33148
2012-08-12 13:27:49 +00:00
Jo-Philipp Wich
9903c3ead8 padjffs2: link statically
SVN-Revision: 33100
2012-08-10 19:26:43 +00:00
John Crispin
ccb6b0a063 tools: clean up Makefiles / make ccache work
SVN-Revision: 29754
2012-01-15 11:43:13 +00:00
Felix Fietkau
e194acb471 padjffs2: fix a compiler warning that makes the build fail because of -Werror
SVN-Revision: 27361
2011-07-02 09:47:19 +00:00
Gabor Juhos
7ce98c6001 tools: create a new tool for more efficient jffs2 padding
SVN-Revision: 27355
2011-07-02 08:37:56 +00:00