From: Rajashree Sankar <rajashree.sankar@sanmina.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Lakshmi Natarajan <lakshmi.natarajan@sanmina.com>
Subject: Re: ISAR SDK Libraries not generated for target
Date: Fri, 26 Mar 2021 09:11:41 +0530 [thread overview]
Message-ID: <CA+UxhRpqMxCak_vPswT3WXdc7ikaNsYpVPUGz8WNC7L8-sRePg@mail.gmail.com> (raw)
In-Reply-To: <20210325170123.0e5515a1@md1za8fc.ad001.siemens.net>
[-- Attachment #1.1: Type: text/plain, Size: 2469 bytes --]
To add in more details ,we need to have libraries built on ARM architecture
which is the target,
Henning Schild,
Can you share us the documentation describing those instructions?
Thanks and Regards,
Rajashree Sankar
On Thu, Mar 25, 2021 at 9:36 PM Henning Schild <henning.schild@siemens.com>
wrote:
> I have never used the SDK feature, but it seems to be set up for
> crossdev and not native (like the buildchroot). You should have a look
> at the documentation, it mentions on how to install libraries for the
> target arch, possibly coming from "isar-apt" or from debian.
>
> I guess the SDK is really just a way to speed things up, you can
> probably also use the buildchroot, copy in that static qemu, configure
> binfmt and chroot into it. That might be a less confusing way if the
> applications do not take too long to compile.
>
> Henning
>
> Am Thu, 25 Mar 2021 18:20:57 +0530
> schrieb Rajashree Sankar <rajashree.sankar@sanmina.com>:
>
> > Hello,
> >
> > We need to generate an SDK in ISAR platform. We are using the
> > command "bitbake <image> -c populate_sdk".The SDK generated has
> > libraries generated for the host system.We need to have it generated
> > for the target. Please provide the necessary data for the same.
> > Thanks and Regards,
> > Rajashree Sankar
> >
>
>
--
CONFIDENTIALITY
This e-mail message and any attachments thereto, is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information. If you are not the
intended recipient of this e-mail message, you are hereby notified that any
dissemination, distribution or copying of this e-mail message, and any
attachments thereto, is strictly prohibited. If you have received this
e-mail message in error, please immediately notify the sender and
permanently delete the original and any copies of this email and any prints
thereof.
ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS
E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the
Uniform Electronic Transactions Act or the applicability of any other law
of similar substance and effect, absent an express statement to the
contrary hereinabove, this e-mail message its contents, and any attachments
hereto are not intended to represent an offer or acceptance to enter into a
contract and are not otherwise intended to bind the sender, Sanmina
Corporation (or any of its subsidiaries), or any other person or entity.
[-- Attachment #1.2: Type: text/html, Size: 3121 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4252 bytes --]
next prev parent reply other threads:[~2021-03-26 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 12:50 Rajashree Sankar
2021-03-25 16:01 ` Henning Schild
2021-03-26 3:41 ` Rajashree Sankar [this message]
2021-03-26 7:03 ` Henning Schild
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=CA+UxhRpqMxCak_vPswT3WXdc7ikaNsYpVPUGz8WNC7L8-sRePg@mail.gmail.com \
--to=rajashree.sankar@sanmina.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=lakshmi.natarajan@sanmina.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