Hi YongQin, You can go to TCWG's FAQ page at https://wiki.linaro.org/WorkingGroups/ToolChain/FAQ (Q7) to get a detailed explanation on the naming conventions and also the difference between gnu and elf.
Hi TCWG guys, Sorry but may I ask a simple question too please. What is the difference between the binaries (eg gcc-linaro-aarch64-linux-gnu-*_linux.tar.*) and the runtime libraries (eg gcc-linaro-aarch64-linux-gnu-*_runtime.*)? Thanks! On Thu, Nov 21, 2013 at 10:29 AM, YongQin Liu <yongqin....@linaro.org>wrote: > Hi, Christophe, Rick > > Thank you for the detail explanation. > Now I think I understand some of them, and can start search for what I > don't know via google. > > Thanks again. > > Best Regards, > Yongqin Liu > > > On 21 November 2013 22:28, Christophe Lyon <christophe.l...@linaro.org>wrote: > >> This is correct. >> The names are derived from the "target triplet" used to configure the >> tools, which describe the target CPU architecture, as well as the >> target OS. >> aarch64: target is AArch64, little endian >> aarch64_be: target is AArch64, big endian >> arm: target is AArch32, little endian >> armeb: target is AArch32, big endian >> >> none-elf and none-gnueabi: bare metal (that is, no target OS) >> linux: target OS is linux >> >> In gnueabihf, the 'hf' means that the ABI variant is the "hard-float" one. >> >> The rest of the naming includes the release number (e.g. 4.8 branch, >> 2013.09 release), and: >> linux: host OS is linux (x86 PC) >> win32: host OS is Windows >> src: source code >> runtime: target runtime libraries >> >> Christophe >> >> >> On 21 November 2013 15:19, Rick <banma...@gmail.com> wrote: >> > >> > Hi YongQin, >> > >> > I think toolchain's name include "linux" means that tool will be used to >> > compile >> > application run on arm with linux OS, if your arm board run linux and >> you >> > want compile an application for it,you can choice this one. >> > >> > the "none" is used to compile bare-metal application,i.e. without OS. >> > >> > Cheers >> > >> > >> > >> > On 11/21/2013 10:04 PM, YongQin Liu wrote: >> > >> > Hi, All >> > Under this site >> > http://releases.linaro.org/13.09/components/toolchain/binaries/, >> > there are many files released. but do we have any description on the >> file >> > naming rules? >> > >> > Sorry for my simple question, I just want to know what the files are >> used >> > for. which one I should select when I need to use toolchain. >> > >> > Like the files below, I can guess that aarch64 means that it will >> generate >> > files run on aarch64 platform, but I can not guess what's the >> difference >> > between linux and none, and not know what's the difference between gnu >> and >> > elf. >> > >> > So if you have any wiki/link about the the naming rules or description >> about >> > the file, >> > please share me. >> > >> > crosstool-ng-linaro-1.13.1-4.8-2013.09-01.tar.bz2 >> > crosstool-ng-linaro-1.13.1-4.8-2013.09.tar.bz2 >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_linux.tar.bz2 >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_linux.tar.xz >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_runtime.tar.bz2 >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_src.tar.bz2 >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_win32.zip >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_win32.zip.xz >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09-20130912_win32.exe >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.tar.bz2 >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.tar.xz >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09_runtime.tar.bz2 >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09_src.tar.bz2 >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09_win32.zip >> > gcc-linaro-aarch64-linux-gnu-4.8-2013.09_win32.zip.xz >> > gcc-linaro-aarch64-none-elf-4.8-2013.09-01_linux.tar.bz2 >> > gcc-linaro-aarch64-none-elf-4.8-2013.09-01_linux.tar.xz >> > gcc-linaro-aarch64-none-elf-4.8-2013.09-01_win32.zip >> > gcc-linaro-aarch64-none-elf-4.8-2013.09-01_win32.zip.xz >> > gcc-linaro-aarch64-none-elf-4.8-2013.09_linux.tar.bz2 >> > gcc-linaro-aarch64-none-elf-4.8-2013.09_linux.tar.xz >> > gcc-linaro-aarch64-none-elf-4.8-2013.09_win32.zip >> > gcc-linaro-aarch64-none-elf-4.8-2013.09_win32.zip.xz >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_linux.tar.bz2 >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_linux.tar.xz >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_runtime.tar.bz2 >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_win32.zip >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_win32.zip.xz >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_linux.tar.bz2 >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_linux.tar.xz >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_runtime.tar.bz2 >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_src.tar.bz2 >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_win32.zip >> > gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_win32.zip.xz >> > gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_linux.tar.bz2 >> > gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_linux.tar.xz >> > gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_win32.zip >> > gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_win32.zip.xz >> > gcc-linaro-aarch64_be-none-elf-4.8-2013.09_linux.tar.bz2 >> > gcc-linaro-aarch64_be-none-elf-4.8-2013.09_linux.tar.xz >> > gcc-linaro-aarch64_be-none-elf-4.8-2013.09_win32.zip >> > gcc-linaro-aarch64_be-none-elf-4.8-2013.09_win32.zip.xz >> > gcc-linaro-arm-linux-gnueabihf-4.8-2013.09-20130912_win32.exe >> > gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.bz2 >> > gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.xz >> > gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_runtime.tar.bz2 >> > gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_src.tar.bz2 >> > gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_win32.zip >> > gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_win32.zip.xz >> > gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_linux.tar.bz2 >> > gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_linux.tar.xz >> > gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_runtime.tar.bz2 >> > gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_win32.zip >> > gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_win32.zip.xz >> > >> > -- >> > Thanks, >> > Yongqin Liu >> > --------------------------------------------------------------- >> > #mailing list >> > linaro-andr...@lists.linaro.org >> > http://lists.linaro.org/mailman/listinfo/linaro-android >> > linaro-validat...@lists.linaro.org >> > http://lists.linaro.org/pipermail/linaro-validation >> > >> > >> > _______________________________________________ >> > linaro-toolchain mailing list >> > linaro-toolchain@lists.linaro.org >> > http://lists.linaro.org/mailman/listinfo/linaro-toolchain >> > >> > >> > >> > _______________________________________________ >> > linaro-toolchain mailing list >> > linaro-toolchain@lists.linaro.org >> > http://lists.linaro.org/mailman/listinfo/linaro-toolchain >> > >> > > > > -- > Thanks, > Yongqin Liu > --------------------------------------------------------------- > #mailing list > linaro-andr...@lists.linaro.org <linaro-...@lists.linaro.org> > http://lists.linaro.org/mailman/listinfo/linaro-android > linaro-validat...@lists.linaro.org <linaro-...@lists.linaro.org> > http://lists.linaro.org/pipermail/linaro-validation > > _______________________________________________ > linaro-toolchain mailing list > linaro-toolchain@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-toolchain > >
_______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
