From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 4/4] PTXdist: be more helpful using the pre-build archive feature
Date: Thu, 23 Jan 2014 10:52:45 +0100 [thread overview]
Message-ID: <1390470765-9417-5-git-send-email-jbe@pengutronix.de> (raw)
In-Reply-To: <1390470765-9417-1-git-send-email-jbe@pengutronix.de>
To make use of this helpful PTXdist feature, help a new user to understand
how to configure her/his project.
Signed-off-by: Juergen Beisert <jbe@pengutronix.de>
---
rules/project-name.in | 18 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git a/rules/project-name.in b/rules/project-name.in
index f546458..ce57364 100644
--- a/rules/project-name.in
+++ b/rules/project-name.in
@@ -164,20 +164,32 @@ config PROJECT_USE_LOCAL_PLATFORM_NAME
The name of the platform to use. This is the directory name of
the platform in the ptxdist workspace e.g. ``platform-i586''.
+comment "------------------------------------"
+comment "pre-build package handling"
+comment "------------------------------------"
config PROJECT_CREATE_DEVPKGS
bool
- prompt "create dev packages"
+ prompt "create pre-build archives"
+ help
+ Enable the creation of pre-build package archives. Read the
+ "How to become a PTXdist Guru" for further details.
config PROJECT_USE_DEVPKGS
bool
select HOST_CHRPATH
- prompt "use dev packages"
+ prompt "use pre-build archives"
+ help
+ Use pre-build package archives to build or re-build the project if
+ corresponding package archives with the same configuration are found.
config PROJECT_DEVPKGDIR
string
- prompt "dev package dir"
+ prompt "pre-build archive directory"
depends on PROJECT_USE_DEVPKGS
default "/opt/OSELAS.BSP/${PTXCONF_PROJECT_VENDOR}/OSELAS.BSP-${PTXCONF_PROJECT_VENDOR}-${PTXCONF_PROJECT}${PTXCONF_PROJECT_VERSION}"
+ help
+ This entry defines the path to a directory where pre-build archives
+ are expected.
endmenu
--
1.8.5.2
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-01-23 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 9:52 [ptxdist] [PATCH] Fix some packages in regard to PTXdist's " Juergen Beisert
2014-01-23 9:52 ` [ptxdist] [PATCH 1/4] QT4/pre-build: installing the examples needs the source tree Juergen Beisert
2014-01-23 10:57 ` Marc Kleine-Budde
2014-01-23 11:38 ` Juergen Beisert
2014-01-23 9:52 ` [ptxdist] [PATCH 2/4] Mono/pre-build: targetinstall needs access to " Juergen Beisert
2014-01-23 9:52 ` [ptxdist] [PATCH 3/4] bluez/pre-build: installing the test scripts needs " Juergen Beisert
2014-01-23 9:52 ` Juergen Beisert [this message]
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=1390470765-9417-5-git-send-email-jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--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