> > The scalcout record comes from the synApps "calc" module. When you
> > build streamDevice your configure/RELEASE file needs to point to CALC
> > if you want to use that record. The details vary between releases of
> > streamDevice. When you build your application you also need to include
> > CALC if you enabled it when building streamDevice.
>
> That'll the the reason then. I have calc installed and built StreamDevice
> with it, but not the application. Still, it feels a bit strange that
> everything appears to continue to run after this error, just the path
> isn't set during initialisation.
Hm, I tried to fix this now by adding CALC to the application (both in the
configure/RELEASE and in the environment), but the record it creates is
still empty. No error messages to be seen during the build, though. What
do I have to check to find out where this is not being picked up properly?
You will have to set CALC to an absolute path pointing to your installation of the calc module in your application's configure/RELEASE file (don't use the environment), and as well add the dbd snippet that calc generates (calcSupport.dbd, including the definition for the scalcout record type) as the name of the library that calc generates (calc, containing the code for the scalcout record type) to the appropriate definitions in your application's Makefile (where the IOC binary is created).
Your best check is to look at the dbd file and the IOC binary your generate in your application: Does the dbd contain (or include) the definition of the scalcout record? Does the shared library list of the binary (output of the ldd command) contain libcalc?
If both answers are yes, your IOC looks good.
Cheers,
~Ralph
