summaryrefslogtreecommitdiff
path: root/target/config/Config.in.binutils
AgeCommit message (Collapse)Author
2016-04-21m68k: default to binutils 2.26Waldemar Brodkorb
2016-03-31xtensa: use latest binutils/gccWaldemar Brodkorb
2016-03-07rework menu based config systemWaldemar Brodkorb
After the addition of bare metal toolchains the menu system allowed to create non-valid configurations. I reworked it so we can also add other operating system support if we wish. So first you choose your operating system, then your architecture and endianess, after that your embedded system, emulator or generic device and then you choose your task you want to run. Tasks may be toolchain, a new appliance/application or some preconfigured sets of packages and configurations as kodi, mpd, firefox and more. The tasks are limited to a plausible choice of hardware and software. Deduplicate CPU configuration. You don't wanna compile Kodi for a H8/300 microcontroller ;)
2016-02-25add basic newlib toolchain support for moxieWaldemar Brodkorb
2016-02-14binutils: use 2.26 only for Xtensa noMMU and H8300Waldemar Brodkorb
2016-02-03add support for binutils 2.26Waldemar Brodkorb
2015-12-26add experimental support for xtensa de212 coreWaldemar Brodkorb
2015-11-30bfin: latest gcc/binutils is working fine. checked with gdb sim and real ↵Waldemar Brodkorb
hardware
2015-10-21remove unneeded split in choice and default, remove ↵Waldemar Brodkorb
ADK_TARGET_KERNEL_VERSION (unused)
2015-03-07reorder libc and toolchain optionsWaldemar Brodkorb
After a short discussion with Phil, I put Libc stuff into Toolchain menu, as it does not belong to Target configuration. Add a Advanced Option menu for specific toolchain related options. I think this change make building OpenADK for beginners simpler. A starter doesn't know anything about different libc, floating settings, ...