From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: A possible bug into linux-custom.inc
Date: Mon, 19 Sep 2022 13:33:54 +0200 [thread overview]
Message-ID: <CAJGKYO4+z8QmZi6UP6qoAEBGtmUBrsOZKgbm1gkyrrRtU=ip7g@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO51FoU1ujc-fh0ycpXeYtq+7XD5ixW7bLUCs8VnbRUvTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Il Lun 19 Set 2022, 11:14 Roberto A. Foglietta <roberto.foglietta@gmail.com>
ha scritto:
> Il Lun 19 Set 2022, 09:20 Henning Schild <henning.schild@siemens.com> ha
> scritto:
>
>>
>> [...]
>
>
> SRC_URI += "file://debian/my_rules.tmpl"
>> do_my_rules() {
>> mv ${WORKDIR}/debian/my_rules.tmpl ${WORKDIR}/debian/rules.tmpl
>> }
>> addtask my_rules after do_unpack before do_transform_template
>>
>
> This seems a good way to go. Thanks, R-
>
A more generalised recipe here below
SRC_URI += " \
file://custom/postinst \
file://custom/rules.tmpl \
"
do_custom_debian_dir() {
cd ${WORKDIR}
mkdir -p debian
for i in ${SRC_URI}; do
i=$(echo "$i" | sed -ne "s,file://\(custom/\),\\1,p")
if [ -f "$i" ]; then mv -f $i debian/; fi
done
cd -
}
addtask custom_debian_dir after do_unpack before do_transform_template
do_prepare_build_prepend() {
rm -rf ${S}/debian
}
N.B.: script are not execute by bash thus substring like ${var/this/that/}
fails. Uhm, why do not use the bash?
Cheers, R-
[-- Attachment #2: Type: text/html, Size: 3089 bytes --]
prev parent reply other threads:[~2022-09-19 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 20:04 Roberto A. Foglietta
2022-09-18 22:06 ` Roberto A. Foglietta
2022-09-19 7:20 ` Henning Schild
2022-09-19 9:14 ` Roberto A. Foglietta
2022-09-19 11:33 ` Roberto A. Foglietta [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='CAJGKYO4+z8QmZi6UP6qoAEBGtmUBrsOZKgbm1gkyrrRtU=ip7g@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/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