From: Roland Hieber <rohieb@rohieb.name>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rohieb@rohieb.name>
Subject: [ptxdist] [PATCH] templates: file: update comments and improve wording
Date: Wed, 12 Dec 2018 00:29:26 +0100 [thread overview]
Message-ID: <20181211232926.22592-1-rohieb@rohieb.name> (raw)
The way of building target packages has changed over the years, and
SYSROOT_TARGET is no longer filled in the install stage. But all of this
is also explained in the Reference Manual, so we don't have to duplicate
that here.
Also add the definition of @PACKAGE@_DIR at the top, which is used in
the targetinstall stage later.
Signed-off-by: Roland Hieber <rohieb@rohieb.name>
---
rules/templates/template-file-make | 45 ++++++------------------------
1 file changed, 9 insertions(+), 36 deletions(-)
diff --git a/rules/templates/template-file-make b/rules/templates/template-file-make
index ee2a612ef..4e322a39c 100644
--- a/rules/templates/template-file-make
+++ b/rules/templates/template-file-make
@@ -4,25 +4,27 @@
#
# See CREDITS for details about who has contributed to this project.
#
# For further information about the PTXdist project and license conditions
# see the README file.
#
#
# We provide this package
#
PACKAGES-$(PTXCONF_@PACKAGE@) += @package@
+@PACKAGE@ := @package@
@PACKAGE@_VERSION := @VERSION@
+@PACKAGE@_DIR := $(PKGDIR)/$(@PACKAGE@)-$(@PACKAGE@_VERSION)
# ----------------------------------------------------------------------------
# Get
# ----------------------------------------------------------------------------
#$(STATEDIR)/@package@.get:
# @$(call targetinfo)
# @$(call touch)
# ----------------------------------------------------------------------------
# Extract
# ----------------------------------------------------------------------------
@@ -44,72 +46,43 @@ PACKAGES-$(PTXCONF_@PACKAGE@) += @package@
# ----------------------------------------------------------------------------
#$(STATEDIR)/@package@.compile:
# @$(call targetinfo)
# @$(call touch)
# ----------------------------------------------------------------------------
# Install
# ----------------------------------------------------------------------------
$(STATEDIR)/@package@.install:
@$(call targetinfo)
-
#
# TODO:
-# If some of the files are required in root filesystem's build process, install
-# these files in the install stage. But use proper variables PTXdist supports
-# to install files, instead of fixed paths. The following variables can be
-# used:
-#
-# - $(PTXDIST_SYSROOT_TARGET) points to a directory tree
-# all target relevant libraries and header files are installed to. All
-# packages built for the target are searching in this directory tree for
-# header and library files. These files are for compile time only, not for
-# runtime!
-# Paths:
-# - executables: $(PTXDIST_SYSROOT_TARGET)/bin
-# - header files: $(PTXDIST_SYSROOT_TARGET)/include
-# - libraries: $(PTXDIST_SYSROOT_TARGET)/lib
-#
-# - $(PTXDIST_SYSROOT_HOST) points to a directory tree all host relevant
-# executables, libraries and header files are installed to. All packages
-# built for the host are searching in this directory tree for executables,
-# header and library files.
-# Paths:
-# - executables: $(PTXDIST_SYSROOT_HOST)/bin
-# - header files: $(PTXDIST_SYSROOT_HOST)/include
-# - libraries: $(PTXDIST_SYSROOT_HOST)/lib
+# If files are needed at compile-time, install those files in the install
+# stage, but use proper variables instead of fixed paths. See the section
+# "Variables Reference" in the PTXdist Reference Manual for a list.
#
-# - $(PTXDIST_SYSROOT_CROSS) points to a directory tree all cross relevant
-# executables, libraries and header files are installed to. All packages
-# built for the host to create data for the target are searching in this
-# directory tree for executables, header and library files.
-# Paths:
-# - executables: $(PTXDIST_SYSROOT_CROSS)/bin
-# - header files: $(PTXDIST_SYSROOT_CROSS)/include
-# - libraries: $(PTXDIST_SYSROOT_CROSS)/lib
-#
-#
-# If no compile time files are reqired, skip this stage
+# If no compile-time files are required, skip this stage.
@$(call touch)
# ----------------------------------------------------------------------------
# Target-Install
# ----------------------------------------------------------------------------
$(STATEDIR)/@package@.targetinstall:
@$(call targetinfo)
#
-# TODO: To build your own package, if this step requires one
+# TODO: for target packages, install files in the target root file system.
+# Otherwise, remove this stage.
+#
# @$(call install_init, @package@)
# @$(call install_fixup,@package@,PRIORITY,optional)
# @$(call install_fixup,@package@,SECTION,base)
# @$(call install_fixup,@package@,AUTHOR,"@AUTHOR@")
# @$(call install_fixup,@package@,DESCRIPTION,missing)
#
# TODO: Add here all files that should be copied to the target
# Note: Add everything before(!) call to macro install_finish
#
# @$(call install_copy, @package@, 0, 0, 0755, $(@PACKAGE@_DIR)/foobar, /dev/null)
#
# @$(call install_finish,@package@)
--
2.19.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2018-12-11 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 23:29 Roland Hieber [this message]
2018-12-12 13:35 ` Michael Olbrich
2019-01-16 10:22 ` Roland Hieber
2019-01-18 8:13 ` Michael Olbrich
2019-01-18 9:01 ` Roland Hieber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181211232926.22592-1-rohieb@rohieb.name \
--to=rohieb@rohieb.name \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox