LPC1114/333 error when making release build

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LPC1114/333 error when making release build

Jump to solution
5,347 Views
tyassin1
Contributor II

Hi,

I am trying to do a build in "release" mode. Everything works fine in "debug" mode.
I go "Project->Build configurations-> Set Active->Release"

When i try to build I get the following error:

c:/nxp/mcuxpressoide_11.6.1_8255/ide/plugins/com.nxp.mcuxpresso.tools.win32_11.6.1.202207200623/tools/bin/../lib/gcc/arm-none-eabi/10.3.1/../../../../arm-none-eabi/bin/ld.exe: cannot find -lCMSIS_CORE_LPC11xx

I use the package: CMSIS_CORE_LPC11xx which is included when making the project.

Any ideas?

Thank you
Thomas

0 Kudos
Reply
1 Solution
5,333 Views
frank_m
Senior Contributor III

So far, yes.
These settings evaluate into paths / file names, the difference in this case is the ../Debug or ../Release subfolder.

Are these folders there, and are the specified libraries there ?
I don't have the LPC1114 or the SDK to check this myself.

However, there is no fundamental difference between the Debug and the Release build, except for the toolchains settings (compiler, linker, pre-/post build), which are configurable.

In case it is missing in the ../Release folder, you should be able to link against the other lib version.

View solution in original post

7 Replies
5,319 Views
tyassin1
Contributor II

Hello,

Yes now it works.
The missing point was the creation of the missing folder "Release" with the file "libCMSIS_CORE_LPC11xx" added in the folder.

Thank you very much to both of you.

0 Kudos
Reply
5,336 Views
tyassin1
Contributor II

Hi,

I have attached a screendumb of the two different settings.
I hope it is the right placed I have looked?

0 Kudos
Reply
5,334 Views
frank_m
Senior Contributor III

So far, yes.
These settings evaluate into paths / file names, the difference in this case is the ../Debug or ../Release subfolder.

Are these folders there, and are the specified libraries there ?
I don't have the LPC1114 or the SDK to check this myself.

However, there is no fundamental difference between the Debug and the Release build, except for the toolchains settings (compiler, linker, pre-/post build), which are configurable.

In case it is missing in the ../Release folder, you should be able to link against the other lib version.

5,333 Views
ErichStyger
Specialist I

In your release build settings, you point to a the library in a folder named 'Release': have you built that library in that Release folder?

0 Kudos
Reply
5,330 Views
frank_m
Senior Contributor III

That would explain it - it is part of the workspace, and must be built separately.

0 Kudos
Reply
5,328 Views
ErichStyger
Specialist I

I wrote a while back an article about this subject, I hope this would be helpful:

https://mcuoneclipse.com/2017/09/19/managing-project-and-library-dependencies-with-eclipse-cdt/

Erich

5,339 Views
frank_m
Senior Contributor III

> .../arm-none-eabi/bin/ld.exe: cannot find -lCMSIS_CORE_LPC11xx

The '-l' flag specifies an additional linker library.
A fixed prefix of "lib" and suffix of ".a" is assumed in this case, i.e. a file "libCMSIS_CORE_LPC11xx.a".
Not sure if that is correct.

I would compare it to the linker settings of the Debug build.

Tags (1)
0 Kudos
Reply