Library search paths

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

Library search paths

420 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by sarmitage on Sat Apr 13 08:06:16 MST 2013
I'm having a problem with the linker not finding a library.

The error message is:
c:/nxp/lpcxpresso_4.3.0_1023/lpcxpresso/tools/bin/../lib/gcc/arm-none-eabi/4.5.1/../../../../arm-none-eabi/bin/ld.exe: cannot find -lCMSISv2_LPC17xx

I have seen the messages here about not using the correct CMSIS version and I don't think that is the problem in my case.

If I go to Properties/Linker/Libraies, I have this under Search Paths:
"${workspace_loc:/CMSISv2_LPC17xx/Release}"

However, this is the generated linker command line:
arm-none-eabi-gcc -nostdlib -Xlinker -Map=GPIO.map -Xlinker --gc-sections -mcpu=cortex-m3 -mthumb -T "GPIO_Release.ld" -o"GPIO.axf"  ./src/IOtest.o ./src/cr_startup_lpc176x.o   -lCMSISv2_LPC17xx

Note that the -L search path is missing from the command line.

The Debug configuration is set up the same way but it correctly generates the -L path in the command line and builds correctly.  I can't seem to make the Release build do the right thing.

Any ideas?  I'm using LPCXpresso 4.30.  I tried upgrading to version 5 hoping to fix this but the LPC-Link debugging was less reliable.
0 Kudos
Reply
4 Replies

392 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by leluno on Sun Apr 14 11:52:31 MST 2013
who is able to read has some advantages, now it is working - thank you very much
0 Kudos
Reply

392 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by TheFallGuy on Sun Apr 14 02:19:01 MST 2013
Read the FAQ?
http://support.code-red-tech.com/CodeRedWiki/LibraryProjects
0 Kudos
Reply

392 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by leluno on Sun Apr 14 00:59:11 MST 2013
i've the same problem:

how can i set the search-path to a directory?

first i add two new directorys "testdir" and "glcd" with file "x.h" to workspace
then i add these directorys to "properties/path and symbols/inludes .../libraries"

now i want to call x.h from a file in "testdir"
why does this not work with
#include "x.h" 

???
0 Kudos
Reply

392 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by R2D2 on Sat Apr 13 08:11:20 MST 2013

Quote: sarmitage
I have seen the messages here about not using the correct CMSIS version and I don't think that is the problem in my case.



#4 of http://knowledgebase.nxp.com/showthread.php?t=2558 :confused:
0 Kudos
Reply