From: Ron Eggler <ron.eggler@mistywest.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Anders Montonen <Anders.Montonen@iki.fi>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] undefined reference problem persists
Date: Mon, 7 Nov 2022 09:57:20 -0800 [thread overview]
Message-ID: <30ec3752-bf3c-86e7-a2d9-32d1771ee2f1@mistywest.com> (raw)
In-Reply-To: <CANNYZj9WvY-ZM2LSTBcrO5-4FZm99UTMVzOoh=ts-V1HOHs5hQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On 2022-11-07 7:20 a.m., Alexander Kanavin wrote:
> On Mon, 7 Nov 2022 at 16:13, Ron Eggler<ron.eggler@mistywest.com> wrote:
>>> Are you able to fulfil that obligation you have under the license?
>> Yes, that will definitely be doable for the recepient if they chose to
>> do so.
> I'm curious as to how though. Are you going to give them a complete
> set of yocto layers and source code for everything that goes into the
> image, so that they can replicate the yocto build? If they choose to
> replace readline with their own version, I don't see any other way.
Exactly, the customer will have full access to the source code incl. the
complete set of Yocto layers and all.
> Note that we are not talking about the manufacturer of the device, we
> are talking about the actual end users who will buy and use the device
> for its intended purpose.
Yes, understood!
--
*RON EGGLER*
Firmware Engineer
(he/him/his)
www.mistywest.com
MistyWest Logo
[-- Attachment #2.1: Type: text/html, Size: 2276 bytes --]
[-- Attachment #2.2: 2018_MistyWest_LogoCombo_FINAL_RGB.png --]
[-- Type: image/png, Size: 43986 bytes --]
next prev parent reply other threads:[~2022-11-07 17:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 7:45 undefined reference problem persists Ron Eggler
2022-11-06 8:14 ` [yocto] " Alexander Kanavin
2022-11-06 15:43 ` Ron Eggler
2022-11-06 8:40 ` Markus Volk
2022-11-06 15:45 ` Ron Eggler
2022-11-06 10:26 ` Anders Montonen
2022-11-06 16:02 ` Ron Eggler
2022-11-06 16:48 ` Anders Montonen
2022-11-06 17:13 ` Alexander Kanavin
2022-11-06 17:36 ` Ron Eggler
2022-11-06 18:12 ` Alexander Kanavin
2022-11-07 1:35 ` Ron Eggler
2022-11-07 8:27 ` Alexander Kanavin
2022-11-07 15:12 ` Ron Eggler
2022-11-07 15:20 ` Alexander Kanavin
2022-11-07 17:57 ` Ron Eggler [this message]
2022-11-07 19:15 ` Alexander Kanavin
2022-11-07 2:19 ` Ron Eggler
2022-11-07 8:32 ` Alexander Kanavin
2022-11-07 1:00 ` Khem Raj
2022-11-07 2:16 ` Khem Raj
2022-11-07 2:30 ` Ron Eggler
[not found] ` <17252C937E759BD8.12191@lists.yoctoproject.org>
2022-11-07 4:19 ` Ron Eggler
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=30ec3752-bf3c-86e7-a2d9-32d1771ee2f1@mistywest.com \
--to=ron.eggler@mistywest.com \
--cc=Anders.Montonen@iki.fi \
--cc=alex.kanavin@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.