Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
Eclipse and mbed: Managed makefile project
Gunnar Arndt.
10
replies
I could help myself: Compiling mbed with the included Python script as described in https://developer.mbed.org/teams/SDK-Development/wiki/Mbed-SDK-build-script-introduction with
python build.py -m UBLOX_C027 -t GCC_ARM
and adding the created binaries to the Eclipse project as shown in the following screenshot did the trick:
It shouldn't be very difficult to adapt this approach for other devices, but it has the obvious disadvantage that it depends on Eclipse - manually created Makefiles, like those used in gcc4mbed, are IDE independent.
Hi again,
I expect to stumble over a tumbleweed each time I come around. Do the cool kids play elsewhere? If so, please let me know ;-)
Or maybe they just don't use Eclipse, who knows...?
However, I'm still trying to complete my mbed Eclipse project described previously. You can download its current working state: /media/uploads/guarndt/c027_base_simple.zip
Please note that you have to check out mbed, compile it as described in the previous post, and import it as a Makefile-based Eclipse project named 'mbed' to fulfill my C027 base project's dependencies. Alternatively, you can add this tiny .project file to your mbed folder and import it to Eclipse: /media/uploads/guarndt/.project.
Your Eclipse Project Explorer should look something like this:
Now, to get to the point, the remaining problem with my project is that I cannot use stuff from the C++ standard library. The following program works fine as long as no object from the libstdc++ is constructed (note the comment in the code):
#include <string>
#include <mbed.h>
std::string str("LED"); // causes linker to fail
int main() {
DigitalOut led(LED);
while (true) {
// printf("%s = %d\n", str.c_str(), led.read());
led = !led;
wait(1);
}
}
If a string, or a vector, or whatever is constructed, or just std::cout is used, linking results in the following error message:
... C:/firedect/git/mbed/build/mbed/TARGET_UBLOX_C027/TOOLCHAIN_GCC_ARM/board.o C:/firedect/git/mbed/build/mbed/TARGET_UBLOX_C027/TOOLCHAIN_GCC_ARM/cmsis_nvic.o C:/firedect/git/mbed/build/mbed/TARGET_UBLOX_C027/TOOLCHAIN_GCC_ARM/mbed_overrides.o C:/firedect/git/mbed/build/mbed/TARGET_UBLOX_C027/TOOLCHAIN_GCC_ARM/retarget.o C:/firedect/git/mbed/build/mbed/TARGET_UBLOX_C027/TOOLCHAIN_GCC_ARM/startup_LPC17xx.o C:/firedect/git/mbed/build/mbed/TARGET_UBLOX_C027/TOOLCHAIN_GCC_ARM/system_LPC17xx.o -lmbed -lstdc++_nano -lsupc++_nano -lgcc -lnosys -lstdc++_nano -lm -lc_nano --start-group -lgcc -lg_nano -lc_nano --end-group --start-group -lgcc -lc_nano --end-group c:/program files (x86)/gnu tools arm embedded/4.9 2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3/armv7-m/crtend.o c:/program files (x86)/gnu tools arm embedded/4.9 2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3/armv7-m/crtn.o -T C:\firedect\git\mbed\libraries\mbed\targets\cmsis\TARGET_NXP\TARGET_LPC176X\TOOLCHAIN_GCC_ARM\LPC1768.ld c:/program files (x86)/gnu tools arm embedded/4.9 2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3/../../../../arm-none-eabi/lib/armv7-m\libc_nano.a(lib_a-signalr.o): In function `_kill_r': signalr.c:(.text._kill_r+0xe): undefined reference to `_kill' c:/program files (x86)/gnu tools arm embedded/4.9 2015q3/bin/../lib/gcc/arm-none-eabi/4.9.3/../../../../arm-none-eabi/lib/armv7-m\libc_nano.a(lib_a-signalr.o): In function `_getpid_r': signalr.c:(.text._getpid_r+0x0): undefined reference to `_getpid' collect2.exe: error: ld returned 1 exit status makefile:57: recipe for target 'C027_Base_simple.elf' failed make: *** [C027_Base_simple.elf] Error 1 17:12:23 Build Finished (took 904ms)
The same error can be provoked by unchecking
Remove unused sections (-Xlinker --gc-sections)
in the linker settings, or by unchecking
Do not use exceptions (-fno-exceptions)
in the C++ compiler settings. Otherwise, I've tried to replicate the settings from the Makefile provided with the C027 Hello World project exported from the mbed online compiler as closely as possible. As using C++ stuff in that project works no problem, I guess I've missed something setting up my project. I know, it's a lot to read, but maybe there are other people interested in using Eclipse, and another pair of eyes to review my stuff would be of great help. Thank you for reading till here, and for any suggestion to come.
Dear Gunnar Arndt,
I've just answered to the similar question here https://developer.mbed.org/forum/mbed/post/40272/
PlatformIO can be integrated to Eclipse IDE too. Also, take a look into this manual "Improvised" FRDM-K64F Eclipse/Platformio Setup
Regards, Ivan.
I'm trying to configure an Eclipse project for my LPC1768-based Ublox C027 with the following requirements:
I'm working in the following environment (installation described here in great detail: https://gnuarmeclipse.github.io/):
My Eclipse's Project Explorer is now looking like this:
The 'mbed' project has been cloned via git and imported to Eclipse without a build configuration or something alike - I'm trying to include it to other Projects by adding its subfolders to the include path there.
As found out here, it seems to be impossible to use the project template 'Hello World ARM Cortex-M C/C++ Project' provided with GNU ARM Eclipse, as it includes unistd.h, which conflicts with mbed: https://developer.mbed.org/forum/bugs-suggestions/topic/17173/
Thus, I'm trying to create a project starting from a simple C++ project in Eclipse, with the GNU ARM toolchain. I've so far tried to replicate the settings from the Makefile taken from a project exported from mbed online, but some settings remain unclear. For example, I get this warning:
The Reset_Handler, as far as my humble understanding reaches, should have been defined by the linker script? Another Problem is that the bin file has only 128 Bytes, whereas the elf file has 35 KB.
You can download my Eclipse project /media/uploads/guarndt/c027_base_simple.zip, but you must not forget to add an 'mbed' project cloned from https://github.com/mbedmicro/mbed to your workspace in addition. I suggest to start with a look at 'C/C++ Build -> Settings -> Tool Settings' in the project's properties.
In general, I have to admit that I'm not sure if my approach of adding the mbed headers as a separate project without a build configuration (maybe as a static library) can work, but I hope that I've only missed a few smaller problems which one of you guys might spot. I'm looking forward to your suggestions - thank you in advance.