eabi

The GCC uses a 4-byte wchar_t by default. I can set the option -fshort-wchar to get 2 bytes per wchar_t in the L"string constants" . But when I set the compiler option to my source file I get the famous warning message foo.o uses 2-byte wchar_t yet the output is to use 4-byte wchar_t ; use of wchar_t values across objects may fail Since I really want 2-byte wchar_t I also want the output to use this variant. Is there any linker option to tell it what I want? Edit This warning doesn't inhibit the linker to produce a valid output. But the dozens of false warnings cover other messages. In

What for do we need ARM EABI v7a System image in Android development? What is the purpose of that particular image? if you work with the NativeDK, without that image the emulator is not able to simulate the execution of ARMv7 code (like multicore-instructions and NEON floating-point-unit) It is the kernel image. You must install it, otherwise the image won't start, failing with ERROR: This AVD's configuration is missing a kernel file The system image is used by the emulator to virtualize the Android OS so Apps can be tested/debugged on a PC without the need to upload the App to a phone

The more I look at this PDF the less I understand what it means. Also I'd like some comments on this others 1 and 2 . An ABI ( Application Binary Interface ) is a standard that defines a mapping between low-level concepts in high-level languages and the abilities of a specific hardware/OS platform's machine code. That includes things like: how C/C++/Fortran/... data types are laid out in memory (data sizes / alignments) how nested function calls work (where and how the information on how to return to a function's caller is stored, where in the CPU registers and/or in memory function arguments

When you build a gcc toolchain there is the possibility to build it as arm-elf or as arm-none-eabi, but what is the difference? I use the eabi today, but that is just since everyone else seem to do that... but since that is a really bad argument, it would be really nice to understand the difference. Note: This toolchain will crosscompile code for Cortex-M3 based mcu:s like the stm32. Thanks Some links : EABI: http://en.wikipedia.org/wiki/Application_binary_interface http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.subset.swdev.abi/index.html ELF: http://en.wikipedia.org/wiki