• State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 19 subscribers
  • Views 1623 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

adding GCC arm .a libraries to a Keil project

BMcK

I successfully built a Keil project using GCC as a tool chain which includes GCC .a library. Now I want to split it into a main file and an the rest of my project built as an additional library. I am having trouble to achieve such goal using uVision. For example, as soon as I add just a path to my second library then linker can't find the first one.  Am I asking for impossible?  

Thanks. 

Parents
  • 0

    Here is the solution: I need to add into the misc section separately -L path\lib\one   -l libname
    Or -l:name.a

    I did not find where it is written that my options are :

    1. -l name      and in this case libname.a file will be searched for;
    2. -l:name.a  and in this case name.a file is the library.

    Why it has to be so convoluted and complicated...This is just a rhetorical question, obviously. Hope this will help someone else in the future. 

Reply
  • 0

    Here is the solution: I need to add into the misc section separately -L path\lib\one   -l libname
    Or -l:name.a

    I did not find where it is written that my options are :

    1. -l name      and in this case libname.a file will be searched for;
    2. -l:name.a  and in this case name.a file is the library.

    Why it has to be so convoluted and complicated...This is just a rhetorical question, obviously. Hope this will help someone else in the future. 

Children
No data