Quote:
Originally Posted by JHale
Getting further.
I no longer get the unknown error, but now I get a massive list of unresolved symbols.
Am I missing some include path?
|
When you download a module, vxWorks needs to connect all the unresolved references in your module.
For example, if your module calls a function named 'foo', then vxWorks must be able to find an address for 'foo'.
The function 'foo' might be part of the vxWorks kernel or it might come from other modules that have already been downloaded.
Include paths are a compile time issue -- where does the compiler look for header files.
Unresolved symbols is a link time issue (in this case dynamic linking) -- the linker is unable to find some data object or function.
Of course, with C++ name mangling, it can be tedious to figure out where the unresolved symbols are supposed to come from.
It may be that you need to statically link your module to some library.