9 years, 10 months ago.

Is there a bug in the export to external toolchain function?

I just exported a project to code red and now I'm seeing a linker error:

/Applications/lpcxpresso_5.0.14_1067/lpcxpresso/tools/bin/../lib/gcc/arm-none-eabi/4.6.2/../../../../arm-none-eabi/bin/ld: cannot find -lmbed

When I look in the archive created by the online compiler I don't see libmbed.a in there anywhere:

% find . -name '*mbed*' ./Debug/mbed ./mbed ./mbed/mbed.h ./mbed/mbed_debug.h ./mbed/mbed_interface.h %

Is there a problem with the export function? I exported one of the GCC options as well to see if it got an mbed library, but I didn't find one there either. Before doing this I updated my mbed library to the latest. Any help?

thanks, steve

2 Answers

9 years, 10 months ago.

Hi Steve, unfortunately, there were a couple of hard-coded library names in the project templates and the library temporarily changed name. Both issues have been addressed.

You can use now the new exporter enabling beta mode here: http://mbed.org/betamode/

The fix should appear live around Monday next week.

Cheers, Emilio

Accepted Answer
Steve Ravet
poster
9 years, 10 months ago.

Ok, so I found the problem. It seems that the release or build procedure for the mbed library was broken starting with release 44, "Complete refactoring of the mbed library to move the target dependent code to a thin well ...". If I look at the files included in release 43 I see that libmbed.a is there. However from release 44 on it is not. I switched to release 43 of the mbed library in my project and I am able to build it both with the online compiler and in code red after exporting.

Thanks Steve for the help with this. I will try this tomorrow or later today to confirm on my end but it sounds like that works.

This is my similar topic http://mbed.org/questions/209/When-trying-to-compile-simple-blinking-p/

posted by Travis Travelstead 06 Jan 2013