toolchain

Source and target have different EABI versions

老子叫甜甜 提交于 2019-12-22 16:37:25
问题 I'm trying to compile a .so file using an ARM toolchain. However I keep getting this error- error: Source object has EABI version 0, but target has EABI version 5 I can't change anything in the tool chain as I have to use the one given. I've never seen this error before. I used this compiler flag - -Wl,--no-warn-mismatch But had to take it out as it broke a lot of other stuff. The compiler flags I'm using are: -fPIC -O2 -marm -march=armv7-a 回答1: Use as -meabi=5 I'm not going to claim I fully

Toolchain to crosscompile Applications for BBB

喜欢而已 提交于 2019-12-22 15:11:26
问题 My native machine is ubuntu based 14.04 LTS x86_64 system, I want to cross-compile applications and QT programs for Beaglebone black, which is an armv7 based system running on Debian 2015 distribution. Which toolchain I should install on my native system, to get this done? 回答1: Here is a very usefull link how to set up the crosscompiler, uboot, kernel and the filesystem for a beaglebone black. If you only want to crosscompiler, then just follow the few code lines in the Crosscompiler chapter

CMake toolchain includes multiple files

百般思念 提交于 2019-12-22 11:05:50
问题 For the reasons irrelevant to mention I would like to be able to include multiple files into toolchain file. Let's say my toolchain contains following: message(STATUS "file1 is ok") include(./build/file2) the file2 contains identification line: message(STATUS "file2 is ok") the CMakeLists.txt contains: cmake_minimum_required (VERSION 2.8.8) project (pro) message(STATUS "cmakelists.txt is ok") I call it using following command: cmake -DCMAKE_TOOLCHAIN_FILE=../../build/file1 ../../ Now, I would

What is the most primitive possible toolchain for android programming?

吃可爱长大的小学妹 提交于 2019-12-22 08:43:32
问题 I feel as though I'm trying to learn android programming in the middle of a fireworks display during a rodeo. All the fancy IDE stuff recommended by all the books I seem to find is just monumentally distracting from discovering what I really and truly need just to develop an android app. Can anyone point me at documentation for the minimal set of the tools needed to actually build an app? I feel like if I could understand what the heck was actually going on, I'd be better able to use the

Using armhf as a secondary toolchain in Yocto

耗尽温柔 提交于 2019-12-20 06:02:52
问题 I am currently working on a board booting in 64 bit mode using aarch64 and I have a u-boot in 32 bit mode, I would use arm-linux-gnueabihf. I looked around but there's no other way than using a secondary toolchain via: open-embedded tutorial to use a secondary toolchain Nevertheless, impossible to make it work. Intel made a layer (meta-tc-icc) but it's old and I didn't manage to make it work neither. Any idea how to configure it ? 回答1: So there's a few ways around this. The general answer for

Where to find nm tool (compiled or source code) for Android

你说的曾经没有我的故事 提交于 2019-12-19 04:25:51
问题 I want to create an application that is able to list all symbols of a dynamic library .so file in Android. I want to ask if there is precompiled nm for Android or at least nm's source code so that I can compile it myself. 回答1: nm is part of binutils. You can get the source code from http://ftp.gnu.org/gnu/binutils. You can also find arm supporting binary (compiled for host, linux-x86) in Android NDK. If you need a binary for Android target, you can try to build it by obtaining latest Android

What's the use of LLVM in Android NDK Toolchains?

﹥>﹥吖頭↗ 提交于 2019-12-18 13:22:54
问题 What's the use of LLVM in Android NDK Toolchains? A little recap: I was building my native project with Gradlew on Ubuntu, targeting arm and x86_64 architectures. Seems that LLVM were utilized to call C/C++ compiler of arm-linux-androideabi-4.9 as well as x86_64 (?) The following is extracted from armeabi-v7a/ndkBuild_build_output.log: /home/mypc/Android/android-ndk-r17c/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ -MMD -MP -MF /home/mypc/git/android-project-1/build/intermediates

getting c++11 - compliant compiler

懵懂的女人 提交于 2019-12-18 11:53:58
问题 This all seems like a colossal mess. All I want is a compiler that implements C++11, so I can use <chrono> . But I'm so confused from the very beginning. Currently, I build programs by invoking G++, but when I check the version via $ g++ -v , I get: gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) What's going on? Am I using G++? GCC? LLVM? I don't even know. Are they the same thing? So now I'm trying to build and download GCC 4.7 via gnu.org, but I have no idea what

Where are the x64 and ARM Developer Prompts for VS2017?

人盡茶涼 提交于 2019-12-17 20:13:17
问题 I installed the Visual Studio 2017 Build Tools. After installation, there's only an x86 Developer Command Prompt when navigating Start → Programs → Visual Studio 2017 → Visual Studio Tools . There are no prompts for x64 and ARM. (Usually there's about 6 developer prompts to choose from). Where are the build tools for x64 and ARM located? UPDATE (JAN-18-2017) After installing the entire Windows 10 SDK, Build 15003 per @magicandre1981 instructions, I cannot find the Developer Prompts. I can't

Determine minimum OSX version a binary was compiled for

独自空忆成欢 提交于 2019-12-17 17:55:21
问题 When using Clang's or GCC's Darwin backends to create executables for OSX, the flag -mmacosx-version-min=version can be used to set the earliest version of OSX the executable will run on. Is there any way to trace back from a given executable which flag was used to compile it? I.e. is there a way to determine which minimum OSX version is targeted by a given executable? 回答1: Use otool -l /path/to/binary and inspect the LC_VERSION_MIN_MACOSX load command; specifically, the version field. For