• State Suggested Answer
  • Locked Locked
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 23 subscribers
  • Views 13771 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

Error: L6218E: Undefined symbol cvWaitKey (referred from main.o)

Cristian CLC

Hi everybody, i am trying to use the OpenCv's libraries with keil and i ve done this:
1. Added a Group called libs where i ve put al the .libs files
2. In the project configuration added all the necesary include paths ( and even more just in case ). libraries, sources, and .h paths

I have created a simple project, which compiles and works perfect without using Opencv libs

But when i try to use this libs i get this error:

Error: L6218E: Undefined symbol cvWaitKey (referred from main.o).

(CvWaitkey is defined in highgui.h which is included at the top of the main file)

It seems preety obvious that the compiler doesnt know where is defined cvWaitKey but i dont know what i am doing wrong because i ve ensured to include the highgui.h in the main file and added the include path in the project configuration.

Any idea?

Thanks!

here u have a print screen:
www.mediafire.com/.../8c7v7kmakvi2f5mfg.jpg

Parents
  • 0 in reply to Cristian CLC

    Libraries are only possible to use if they has the correct file format, and are compiled for the correct processor and is compiled to use the same ABI (Application Binary Interface).

    And if the library has hardware dependencies then it must also be compiled for the correct hardware platform.

    That is a reason why lots of libraries are distributed in source form, so the user can rebuild the libraries using the correct compiler tool chain and after having configured the source code to match the used hardware platform.

Reply
  • 0 in reply to Cristian CLC

    Libraries are only possible to use if they has the correct file format, and are compiled for the correct processor and is compiled to use the same ABI (Application Binary Interface).

    And if the library has hardware dependencies then it must also be compiled for the correct hardware platform.

    That is a reason why lots of libraries are distributed in source form, so the user can rebuild the libraries using the correct compiler tool chain and after having configured the source code to match the used hardware platform.

Children