I would like to know if there has suggestion MIPS toolchain version for Cobalt.
Or after which MIPS version is suitable for compiling source code?
Thank you.
Cobalt is know to build successfully for MIPS targets with GCC 4.9.
That said, it should be possible to build Cobalt with any C++03-compliant toolchain.
Related
I'm using a MIPS cross compiler on my Linux machine which works great.
Now I need to compile the same application on Windows.
I'm searching the web for some prebuilt MIPS cross compiler (with toolchain) for MS-Windows, but without success.
Since I'm not sure how to do so, I'm asking if someone knows such prebuilt toolchain? or some guide how to convert my Linux toolchain for windows if it's possible?
Thanks.
You should use Codescape MIPS SDK.
It looks like Mentor has taken away the free MIPS toolchain from the CodeSourcery distribution. Maybe one of these might still work: https://www.linux-mips.org/wiki/Toolchains.
I have been doing some bare metal programming in 32-bit iMX6q SABRE-SD board(arm Cortex-A9). I have used "arm-none-eabi" as the Toolchain. Now, I would like to port all the codes i have written to 64-bit arm Cortex-A57 (R-Car M3 board). How would i select the compiler for this task. Can i use the same compiler with some flag changes for compiling for 64-bit design. Or Will there be any specific compiler provided by the manufacturer.
How would someone select the compiler for his/her embedded design.
Please Help.
Regards,
Ajmal
For compiling into 64-bit architecture, linaro gcc tool could be used:
Please refer to this link:
https://community.arm.com/dev-platforms/f/discussions/5274/issue-compiling-armv8-assembly
I would like to know what they mean with "prebuilt gcc"?
gcc is the compiler, but what do they mean by prebuilt? And why does google offer a prebuilt gcc for their android. Can I just not use the regular gcc?
GCC has a source code repository available via SVN.
In some scenarios, you need to download the source code and build the GCC yourself (specially when you have custom hardware). But for most cases, 'pre-built' GCC for your hardware and OS is enough.
Is it possible to compile native GCC for ARM (host == target == ARM) using Code Sourcery G++?
If it is not possible, could I use crosstool-NG to build the cross-compile and then using this one for compiling the native ARM GCC?
Thank you,
Edit: as to why: I'm creating my own distro for beagleboard...
CodeSourcery provides prebuilt toolchains only for Linux/x86 and Windows (see "Host System Requirements" here). If you want a native ARM-hosted toolchain, you should be able to build one using a cross-compiler. If you want a prebuilt one, you can try some of the existing ARM distros such as Debian-arm, or Aboriginal Linux (it's made to be run in QEMU but you can probably extract the compiler from it and run natively).
Tiny C Compiler runs decently natively on the kindle 3.
Find it on the mobileread forums compiled for native use.
Code sourcery toolchain works for simple comilation via "arm-none-linux-gnueabi-gcc foo.c" IIRC with no effort. creating native arms. Crosstools-ng as well but neither natively AIUI.
I looked into http://buildroot.uclibc.org/downloads/manual/manual.html#_about_buildroot
for a more comprehensive solution.
There are some options in there for what you require IIRC using x-compile to make the compiler but Crosstools is the more robust chain I had trouble with codesourcery doing true static build. HTH
better off to use openembedded
I'm developing a GPS application under Linux, with ARM7 microprocessor.
Which compiler do you recommend? Do you know if there is any toolkit with libraries ready to develop GPS applications?
A friend of mine recommended gcc... what do you guys think about it?
Thank you
I don't think that the compiler matters that much. What is more important is your precise understanding of the library you are using, or of the actual device you are invoking.
However, I will recommend GCC, and I do recommend using a very recent version of GCC. For instance, GCC 4.6.2 is appearing these days, and there have been lot of work recently put in GCC to improve its perfomance for ARM processors. So, if possible, us a 4.6 GCC, not a 4.3 one (some hardware vendors don't give recent GCC with their ARM development kit; you should consider in that case building your GCC (and perhaps binutils) from their source code.
I know nothing about GPS itself.