Would like to confirm hierarchy for a CVI library loaded into project via its *.fp file

[JumperBones]

Hello everyone,

I know there is an order for which library code is loaded via its *.fp file, which I lonce earned a long, long time ago, and I just looked for this in the CVI 8.5 help, but could not find it.

I believe it goes like this, but could someone please confirm?

"If your CVI project has a *.fp file in it, and that *.fp file has various source or binary code to attach to that is in the *same* directory that the *.fp file is located, the the CVI projecty will first link tothat library via its *.dll file (assuming that its companion *.lib file is also there), but failing that, it will link to its *.dll file that is in the operating system's search path (via that same *.lib file mentioned earlier, assuming it is of the same vintage as that *.dll), and failing that, it will link to its *.obj file, and failing that, it will link to its *.c file (so you end up with "live" source to that library in your project)."

In the statement above, the asterisk is a placeholder for the libray file name, such as MyLibrary, and I think it might even be a case-sensitive library name, not sure about that however...

JB

[LuisG]

Hi JB,

One point to remember is that the .fp has no direct association with .dll files. The association is with .lib, .obj, or .c files. If the .lib happens to be an import library for a .dll (as opposed to a static library) then the .lib will in turn be associated with a .dll, but that association is created by the linker, and the search rules for the .dll at runtime are determined by the operating system.

The order of precedence for associating program files with an .fp file is: .lib, .obj, .c. You can verify which one is associated at any given time by clicking Instrument>>Edit and then click the Show Info button. You can also override whatever is attached and attach the source, if you need to debug the code.

In general, the program file needs to be next to the .fp, but there are some exceptions to this. For example, if the .fp is an installed IVI instrument driver, or a VXI pnp driver, or if it supports multiple compatibility modes (msvc and borland sub-folders).

Hope this helps

Luis