From: Henning Schild <henning.schild@siemens.com>
To: Rajashree Sankar <rajashree.sankar@sanmina.com>
Cc: isar-users <isar-users@googlegroups.com>,
Lakshmi Natarajan <lakshmi.natarajan@sanmina.com>
Subject: Re: ISAR SDK Libraries not generated for target
Date: Thu, 25 Mar 2021 17:01:23 +0100 [thread overview]
Message-ID: <20210325170123.0e5515a1@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CA+UxhRqj_ggdUJi0N3DQ5VD6RU-A9JgL2KtwmeXX2CFZ5oRtvQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
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
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7821 bytes --]
next prev parent reply other threads:[~2021-03-25 16:06 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 [this message]
2021-03-26 3:41 ` Rajashree Sankar
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=20210325170123.0e5515a1@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=lakshmi.natarajan@sanmina.com \
--cc=rajashree.sankar@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