toolchain

Cross compilation: special cross compiler or just gcc with option -march?

谁都会走 提交于 2019-12-07 06:46:32
问题 I need to compile a program for Raspberry PI 3+ on Linux machine, and code must be compliant with c++17 standard. Official toolchain is outdated and lack c++17 compilation option. Two solutions that I can see right now are: 1) gcc has an option -march, which described here: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html 2) Installing arm-linux-gbueabi-gcc package, as proposed here: Cross-compiling for Raspberry pi with modern gcc What is the difference between two options? Is there some

What is the state of C99 support in major compilers / toolchains?

大兔子大兔子 提交于 2019-12-06 23:01:24
问题 A response to a comment I made here made me stop and think: "I don't really know what the state of C99 support is." Wikipedia gives details for a few compilers, but I'm not familiar enough with C99 to know all the bits and pieces of the standard, so I'm looking for a gestalt overview answer to the question: What is the state of C99 support in major compilers / toolchains? 回答1: MSVC: Intentionally not implemented unless it overlaps with C++ GCC: Most of the useful parts are in (and have been

Difference between arm-none-eabi and arm-linux-gnueabi?

夙愿已清 提交于 2019-12-06 22:40:13
问题 What is the difference between arm-none-eabi and arm-linux-gnueabi? I know the difference in how to use them (one for bare metal software, the other one for software meant to be run on linux). But what is the technical background? I see there is a difference in the ABI which is, as far as I understood, something like an API but on binary level. It ensures interoperability of different applications. But I don't really understand in which way having or not having an operating system affects my

Compiling Android NDK with Objective-C-enabled gcc errors

让人想犯罪 __ 提交于 2019-12-06 14:42:42
问题 I am working off of Jackie Gleason's presentation about getting objective-c to compile on Android as well as Michael f1337's blog post on the same subject (with the addition of working on Mac OS X, which I am). The major difference between their posts and mine is that I am working to use the latest NDK (r8b). I have followed these steps: 1) Download the latest NDK here: http://developer.android.com/tools/sdk/ndk/index.html 2) Create a directory called NDK, and unpack the download here. 3) In

Source and target have different EABI versions

馋奶兔 提交于 2019-12-06 07:30:32
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 Use as -meabi=5 I'm not going to claim I fully understand it... :-) but it solved the problem. What I was trying to do that failed: assemble with GNU AS

Toolchain to crosscompile Applications for BBB

做~自己de王妃 提交于 2019-12-06 07:30:01
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? 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 https://eewiki.net/display/linuxonarm/BeagleBone+Black To cross-compile applications you need to use the '

CMake toolchain includes multiple files

别等时光非礼了梦想. 提交于 2019-12-06 00:33:25
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 expect the following output: -- file1 is ok -- file2 is ok -- cmakelists.txt is ok Yet I get this: --

What is the most primitive possible toolchain for android programming?

为君一笑 提交于 2019-12-05 14:21:06
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 fancy IDE. Primitive? So, not Eclipse, and also not ant. You can use aapt, javac, dx, apkbuilder, and

Cross compilation: special cross compiler or just gcc with option -march?

此生再无相见时 提交于 2019-12-05 12:06:24
I need to compile a program for Raspberry PI 3+ on Linux machine, and code must be compliant with c++17 standard. Official toolchain is outdated and lack c++17 compilation option. Two solutions that I can see right now are: 1) gcc has an option -march, which described here: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html 2) Installing arm-linux-gbueabi-gcc package, as proposed here: Cross-compiling for Raspberry pi with modern gcc What is the difference between two options? Is there some other possibilities that will work? If you want full Cross Compiler c++17 standard for your Raspberry

What is the state of C99 support in major compilers / toolchains?

本秂侑毒 提交于 2019-12-05 03:39:27
A response to a comment I made here made me stop and think: "I don't really know what the state of C99 support is." Wikipedia gives details for a few compilers, but I'm not familiar enough with C99 to know all the bits and pieces of the standard, so I'm looking for a gestalt overview answer to the question: What is the state of C99 support in major compilers / toolchains? MSVC: Intentionally not implemented unless it overlaps with C++ GCC: Most of the useful parts are in (and have been for awhile). Some missing features. clang: Claims full C99 support 来源: https://stackoverflow.com/questions