Quote:
Originally Posted by taichichuan
Hmm.. The issue is that the symbol be resolved to a working version of the code. I'm not entirely sure of how the Java and Labview code accomplishes this on VxWorks, but as long as those symbols are in the symbol table before your code is loaded, then all should be good.
Alternatively, you can accomplish this by actually linking your code against the WPILib before loading to VxWorks. In the WRS project properties, there is an option to add additional libraries to be linked against. Simply add the WPILib as one of the libraries. At worst, there may be some duplication of code. But, as long as the symbol is resolved to a working block of code, then it should work fine.
HTH,
Mike
|
WPILib is already referenced, I just put the code in a simpletemplate example and changed the out name
LV and Java have their own libraries that don't link to the C versions (Except the camera)
I think the issue is that there is duplication of code and therefore, duplication of work done. I'm guessing that calling DS::getinstance creates a second Ds that prevents the first from hearing anything