Hi Rex,
Sorry, I've been unable to post over the last few days to help out due to some additional projects I've been working on. However, I'm back now and I think I can help a litte. So The process I linked to earlier says to go through these following steps:
- Compile and FTP your *.out shared library to the real time target.
- Compile a stub DLL using the same function prototypes as those exported by the *.out shared library. A stub DLL typically only contains the function prototype themselves without any implementation (ie, empty functions.) This stub DLL will only be used on your Windows host machine, and must have the same name as the original *.out shared library - for example: foo.dll and foo.out.
- Place a Call Library Function Node on your block diagram and specify foo.* as the Library name or path. On the host machine, LabVIEW will find foo.dll, but on the real time target the executable/VI will find foo.out.
- The stub DLL must have the same path relative to the VI in the host development environment as the executable/VI on the real time target
I think your okay with Steps, 1, 3, and 4 and your really just asking how do I create a Stub dll right? So, basically to create a stub you need to compile a stub DLL using the same function names and arguments as those exported by the *.out shared library. This is also done with our some PDA targets and I found a good example here, with C code to give you the general idea.
Basically the Stub code will look like this (with includes removed):
#define DLLEXPORT __declspec(dllexport)
#define EXTERNC extern "C"
/* LvSysBatteryInfo - StubDll function that calls to SysBatteryInfo in SysManger.h in PalmOS API.
See PalmBatt.c for actual function.*/
EXTERNC DLLEXPORT unsigned short LvSysBatteryInfo (unsigned char set,unsigned short *warnThresholdP,
unsigned short *criticalThresholdP, unsigned short *maxTicksP,
unsigned char *kindP, unsigned char *pluggedIn, unsigned char *percentP)
{
return 0; //Actual code for function is in PalmBatt.c
}
And the Associated C code will look something like this (with includes removed):
UInt16 LvSysBatteryInfo (Boolean set,UInt16 *warnThresholdP, UInt16 *criticalThresholdP, Int16 *maxTicksP,
SysBatteryKind *kindP, Boolean *pluggedIn, UInt8 *percentP)
{
return SysBatteryInfo (set, warnThresholdP, criticalThresholdP, maxTicksP, kindP, pluggedIn, percentP);
}
The creation of the Stub is really so that LabVIEW RT does not pop up a warning message when you try to deploy your application that it does not recognize the .out file. I belive you can just ignore the pop up message and everything will run fine provided you have ftped the .out file to your RT target. Let me know if that makes sense or if you have issues trying to get this up and running.
Regards,
Basset Hound
