From: Jan Kiszka <jan.kiszka@siemens.com>
To: Balasubramanian Sundaram <balasubramanian.sundaram@sanmina.com>,
isar-users@googlegroups.com
Subject: Re: Re : integrate bluez with ISAR
Date: Thu, 10 Nov 2022 17:12:04 +0100 [thread overview]
Message-ID: <e75f8561-528f-aeb9-58a0-3fc674a548b4@siemens.com> (raw)
In-Reply-To: <CAMxE6KnVtJAumY7YiwVX5xUi+HGVjogz4qatrMyNh3ZJEYZBYg@mail.gmail.com>
On 10.11.22 13:37, 'Balasubramanian Sundaram' via isar-users wrote:
> Hi Team,
>
> Iam using ISAR build system i'm trying to integrate bluez but iam
> getting following error
> image.png
> and this is my bb file for it anything is missing
> image.png
I think this question was raised elsewhere already, but it is very
essential: WHY do you want to fork bluez away from Debian mainline? You
will inherit maintenance and testing efforts that can be critical,
specifically for product development. If you have a bug report against
bluez or the Debian package, file that first. Ideally, the issue will be
resolved and the new package will be available before you are done with
rebuilding your own one.
Jan
PS: Please share logs, not screenshots, whenever technically possible
(like in this case).
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-11-10 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 12:37 Balasubramanian Sundaram
2022-11-10 13:36 ` Schaffner, Tobias
2022-11-10 13:38 ` Roberto A. Foglietta
2022-11-10 16:12 ` Jan Kiszka [this message]
2022-11-11 7:32 ` Balasubramanian Sundaram
2022-11-11 7:52 ` Uladzimir Bely
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=e75f8561-528f-aeb9-58a0-3fc674a548b4@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=balasubramanian.sundaram@sanmina.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