x64_MT9V034_vid\Debug/../src/main.cpp:142: undefined reference to `ArduCam_writeSensorReg'
\x64_MT9V034_vid\Debug/../src/main.cpp:143: undefined reference to `ArduCam_writeSensorReg'
\x64_MT9V034_vid\Debug/../src/main.cpp:145: undefined reference to `ArduCam_writeSensorReg'
x64_MT9V034_vid\Debug/../src/main.cpp:197: undefined reference to `ArduCam_close'
The definitions are in the .h file, on manual inspection. I've checked my spelling, etc. What is going on here? Is it possible I need to be scrutinizing the library files instead? And when one gets undefined ref is it more likely an include cause or a library cause?
Undefined reference means the linker cannot find the binary code representing that function.
To get as far as trying to link, the compiler must have finished. So the compiler was able to find the declaration of the function.
The definitions are in the .h file, on manual inspection.
Clearly not. I expect the declarations are in the .h file
The problem is one of the following:
1) You meant to write these functions yourself and you haven't
2) The functions are written but you're not compiling and linking the file they're in
3) The functions are in a library and you're not linking against that library.
That is right on the money Repeater I've been delving into that library pretty hard. They released another much smaller and lightweight version, and if I go include crazy its going to get bloated all over. Thank you for clarifying.
I get confused when we use the words "linking against that library". Aren't we just linking to the library.? What's 'against' mean in this context? I am not suggesting you are incorrect, just my linguistics need some polishing -- what does against the library mean? I am probably doing it already and my words haven't caught up with my actions.
You would also benefit greatly from understanding how plain text files become executable binaries and libraries. This would enable you to diagnose the problems in building yourself.