Dear Zephy development team,

your Getting Started Guide [1] tells at some point to download a SDK, make it
executable, run it:
Run the installation binary, type:

$ chmod +x zephyr-sdk-0.7.2-i686-setup.run

$ sudo ./zephyr-sdk-0.7.2-i686-setup.run

Looking into this file I realized that it contains a big block of binary data.
I'm feeling somehow uncomfortable with just executing a binary from an unknown
source (particular with sudo). Is there another way to install this SDK with
non binary data (I'm willing if build it myself) or to tell me what this SDK
apart from cross-compiler-toolchains contains?

What additional tools apart from a cross-compiler toolchain are required
anyway (and why) for your OS?

Thanks,
Oleg


[1] https://www.zephyrproject.org/doc/getting_started/installation_linux.html#installing-requirements-and-dependencies

Oleg,




On 20/02/2016, 08:35, "Oleg Hahm" <oliver.hahm(a)inria.fr> wrote:

Dear Zephy development team,

your Getting Started Guide [1] tells at some point to download a SDK, make it
executable, run it:
Run the installation binary, type:

$ chmod +x zephyr-sdk-0.7.2-i686-setup.run

$ sudo ./zephyr-sdk-0.7.2-i686-setup.run

you can also install without sudo in your home directory or any other location. The script will only extract the contents of the file.

Looking into this file I realized that it contains a big block of binary data.
I'm feeling somehow uncomfortable with just executing a binary from an unknown
source (particular with sudo). Is there another way to install this SDK with
non binary data (I'm willing if build it myself) or to tell me what this SDK
apart from cross-compiler-toolchains contains?

We do have instructions on how to build the SDK yourself, I can’t find the pointer right now, but will add this to the documentation for easy access. The SDK itself is built using Yocto.
The Zephyr SDK is provided to help you getting started with all supported platforms, however, you should be able to use other cross-compilers installed on your system if you wish.

What additional tools apart from a cross-compiler toolchain are required
anyway (and why) for your OS?

The SDK contains cross-compiler toolchains for all supported architectures and host tools. Additionally it contains hosts tools like python, gcc, make, openocd.



Anas

Thanks,
Oleg


[1] https://www.zephyrproject.org/doc/getting_started/installation_linux.html#installing-requirements-and-dependencies

Hi Anas!

Thanks for the fast response!

On Sat, Feb 20, 2016 at 01:47:19PM +0000, Nashif, Anas wrote:

Looking into this file I realized that it contains a big block of binary data.
I'm feeling somehow uncomfortable with just executing a binary from an unknown
source (particular with sudo). Is there another way to install this SDK with
non binary data (I'm willing if build it myself) or to tell me what this SDK
apart from cross-compiler-toolchains contains?

We do have instructions on how to build the SDK yourself, I can’t find the
pointer right now, but will add this to the documentation for easy access.
The SDK itself is built using Yocto.

Thanks for the explanation and looking forward for the pointer.

The Zephyr SDK is provided to help you getting started with all supported
platforms, however, you should be able to use other cross-compilers
installed on your system if you wish.

That's what I somehow assumed. Would be good to know, which variables have to
be set to use the existing toolchains. Or maybe you good even provide
something like a Makefile.toolchain.gcc, so that I can compile withe usual gcc
toolchains for ARM and x86.

What additional tools apart from a cross-compiler toolchain are required
anyway (and why) for your OS?

The SDK contains cross-compiler toolchains for all supported architectures
and host tools. Additionally it contains hosts tools like python, gcc, make,
openocd.

Okay, so this is more an optional prerequisite. Most embedded developers will
have these tools already installed, I guess.

Cheers,
Oleg

P.S. The path to the sample apps as described here
https://www.zephyrproject.org/doc/getting_started/building_zephyr.html also
seems to have changed. It's not "$ZEPHYR_BASE/samples/hello_world/microkernel"
any more, but "$ZEPHYR_BASE/samples/microkernel/apps/hello_world".