ISAR Populate SDK

[Rajashree Sankar <rajashree.sankar@sanmina.com>]

[-- Attachment #1.1.1: Type: text/plain, Size: 1621 bytes --]

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.

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.

[-- Attachment #1.1.2: Type: text/html, Size: 1850 bytes --]

[-- Attachment #1.2: README.sdk --]
[-- Type: application/octet-stream, Size: 1299 bytes --]

Building applications for targets in ISAR takes a lot of time as they are built under QEMU.
SDK helps to develop applications for target platform in crossbuild environment.

SDK contains cross-toolchain for target architecture and a copy of isar-apt repo with
locally prebuilt target debian packages.

 - First one have to mount the system directories for proper operation in chroot environement.
Just call supplied with sdk tarball  in  udo rootfs as an argument to the script `mount_chroot.sh`:

$ sudo mount_chroot.sh  <sdk_rootfs>

 - chroot to isar SDK rootfs:

$ sudo chroot <sdk_rootfs>

 - Check that cross toolchains are installed

:~# dpkg -l | grep crossbuild-essential-armhf
ii  crossbuild-essential-armhf           12.3                   all          Informational list of cross-build-essential packages

 - Install needed prebuilt target packages.

:~# apt-get update
:~# apt-get install libhello-dev:armhf

 - Check the contents of the installed target package

:~# dpkg -L libhello-dev
/.
/usr
/usr/include
/usr/include/hello.h
/usr/lib
/usr/lib/arm-linux-gnueabihf
/usr/lib/arm-linux-gnueabihf/libhello.a
/usr/lib/arm-linux-gnueabihf/libhello.la
/usr/share
/usr/share/doc
/usr/share/doc/libhello-dev
/usr/share/doc/libhello-dev/changelog.gz
/usr/share/doc/libhello-dev/copyright
~#

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4209 bytes --]