From: Daniel Machon <dama@universal-robots.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Custom recipe, multiple machines for same arch
Date: Wed, 3 Mar 2021 11:37:09 +0000 [thread overview]
Message-ID: <e5580bbe730e4bd2a9527b96118fa482@universal-robots.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1722 bytes --]
Hi,
Is there an elegant way to handle custom recipes, that are used in multiple machines that target the same architecture.
Currently when I try to execute a multi-machine build, it fails with: Detect multiple executions of ..
You can get around this by changing PN = recipe-name-${MACHINE} in each custom recipe and IMAGE_INSTALL += recipe-name-${MACHINE}
I am just wondering whether this is the best solution, or if there are any alternatives?
Best regards
Daniel
Med venlig hilsen / Best regards
Daniel Machon
Embedded Linux Engineer
R&D Department
[cid:UR_New_Logo_266cf885-8c99-4fe9-bae0-ff88fedf0005.png]
Universal Robots A/S
Energivej 25
5260 Odense S
Phone: +45 89 93 89 89
Cell: +45 27 99 72 32
dama@universal-robots.com<mailto:dama@universal-robots.com>
www.universal-robots.com<http://www.universal-robots.com>
Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.
If Universal Robots A/S processes personal data relating to physical persons, such processing will meet the requirements of applicable data protection legislation.Please see our Privacy Policy here.<https://www.universal-robots.com/about-universal-robots/privacy-policy/>
[-- Attachment #1.2: Type: text/html, Size: 5020 bytes --]
[-- Attachment #2: UR_New_Logo_266cf885-8c99-4fe9-bae0-ff88fedf0005.png --]
[-- Type: image/png, Size: 3508 bytes --]
next reply other threads:[~2021-03-03 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 11:37 Daniel Machon [this message]
2021-03-03 12:04 ` Jan Kiszka
2021-03-03 12:05 ` Jan Kiszka
2021-03-05 8:21 ` Daniel Machon
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=e5580bbe730e4bd2a9527b96118fa482@universal-robots.com \
--to=dama@universal-robots.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