On Sun, Oct 23, 2016 at 7:00 AM, Robert P. J. Day <rpj...@crashcourse.ca> wrote: > > more of the pedantic nitpickery you've all come to expect from me, > but in section 1.1 of SDK Manual (v. 2.2): > > "All SDKs consist of the following: > > Cross-Development Toolchain: This toolchain contains a compiler, > debugger, and various miscellaneous tools. > > Libraries, Headers, and Symbols: The libraries, headers, and > symbols are specific to the image (i.e. they match the image). > > Environment Setup Script: This *.sh file, once run, sets up the > cross-development environment by defining variables and preparing > for SDK use. " > > hang on ... that last reference to an ".sh" file is potentially > misleading. the generated SDK itself is bundled into the installation > script (say, > poky-glibc-x86_64-core-image-minimal-ppce300c3-toolchain-2.2.sh), and > when that's run, what is installed contains, at the top level, the > setup script "environment-setup-ppce300c3-poky-linux" -- there is no > .sh script installed in the SDK installation directory.
it should really be something like "This shell script file, once sourced ..." fell free to send a patch and cc Scott. > > it might be common to create the symlink for convenience: > > environment-setup-ppce300c3-poky-linux -> env.sh > > or something like that, but AFAICT, there is no ".sh" setup script in > the SDK installation directory. > > is it possible the author was conflating the installation .sh file, > and the environment setup file? > > rday > > -- > > ======================================================================== > Robert P. J. Day Ottawa, Ontario, CANADA > http://crashcourse.ca > > Twitter: http://twitter.com/rpjday > LinkedIn: http://ca.linkedin.com/in/rpjday > ======================================================================== > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto