public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Rajashree Sankar <rajashree.sankar@sanmina.com>,
	isar-users <isar-users@googlegroups.com>
Cc: Lakshmi Natarajan <lakshmi.natarajan@sanmina.com>
Subject: Re: ISAR Populate SDK
Date: Mon, 9 Nov 2020 11:30:51 +0100	[thread overview]
Message-ID: <36fa49c5-3b1a-a258-a2d0-02b440208d57@siemens.com> (raw)
In-Reply-To: <CA+UxhRpj7zHX4XM=FfWmbur5hY=nmzv4E73G_3FPsrWycehtXw@mail.gmail.com>


On 09.11.20 10:19, Rajashree Sankar wrote:
> Hello All,
> In the ISAR framework,we ran the command to generate SDK
>   *bitbake <image_name> -c populate_sdk*
> There was an sdkchroot folder generated in tmp directory.
> The instructions given in the readme of this folder tells us to use
> rootfs of the target.
> Should we specify the rootfs  folder of the generated image? If not
> Please give us detailed instructions.

You get the SDK as tarball under build/tmp/deploy/images. This one can
be distributed, unpacked by the recipient, and its usage is then
documented in the contained readme. That can be considered to be a lot
like Yocto/Buildroot toolchains when using the relocate script. Note
that the latter feature was merged only last week, so you may want to
update your Isar version.

> 
> I have attached the readme file for  reference.
> 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.

Please turn this off, it cannot apply to public lists.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

      reply	other threads:[~2020-11-09 10:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09  9:19 Rajashree Sankar
2020-11-09 10:30 ` Jan Kiszka [this message]

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=36fa49c5-3b1a-a258-a2d0-02b440208d57@siemens.com \
    --to=jan.kiszka@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