niseCfg library link errors - will not compile working code on replicate system

[rjohnson]

i have working software trying to install on a replicate system.    it does not compile on the replicate system.   the problem is nise, niseCfg link errors  for example:  

Undefined symbol:  '_niseCfg_GetVirtualDeviceProperty@20' referenced in "TestSystem_Config.c"

originally it complained it couldn't find the nise.h and niseCfg.h header files.   i copied the header and some other object and fp files (yeah, yeah, i know 😕 from my working system to the replicate system (in the NI/Shared/CVI directory path).

it then found the header file and prototypes but now the undefined link errors.   i have nise.dll in my WIndows System directory.

Please help.   what do i do to fix this?   thanks!

[RobertoBozzolo]

Maybe there's some object file missing to link functions from your fp. If the instrument is installed in CVI, going to Instrument >> Edit..., selecting the instrument and clicking on Show Info... button will show a panel that lists both the function panel and the program file associated to that instrument.

[rjohnson]

thanks for the reply.   that indirectly helped me to solve the problem (at least temporarily).

the instrument panels in both the working original, and the non-working replicates appeared identical, and there was nothing related to nise/niseCfg that i could add in the instrument panel that helped.  

but thinking along this line, i then added the niseCfg.fp to the project and the nise.lib as well, and (because i had copied all the missing files in <Shared>/CVI/ directory to the replicate) it started working.    for some reason, the original did not need to have the niseCfg.fp or the nise.lib be explicitly called, it could find what it needed anyhow.   but now the replicates work, and the original is unaffected by adding those references to the project.

this is a temporary solution, i need to find out why (some) replicate systems are missing a lot of  <Shared>/CVI components, but further investigation has turned up that the replicates in question had their image reinstalled, so the root problem is most probably on my end, not NI.

[rjohnson]

(double post , disregard)

[RobertoBozzolo]

The CVI IDE needs to know someway where to find the resources your program is using and this can be done in several ways. One of them is loading the instruments in the Instrument menu: this is valid if your instrument is used in only one project of yours or a few one. Another method, which is useful for insrtument you use intensively in all your projects, is to add them to the Library menu (option Customize...): this will make your libraries and FPs available for every project you are working on without need to explicitly add the instruments to the Instrument menu.

If you are using an instrument and you don't see it in the project it must be loaded in one of the ways I described before: you can check in the original system which method was used.