LabWindows/CVI 64-builds and FP files

[MM_RohdeSchwarz]

Hi,

I have a project in LabWindows/CVI 2017 64-bit with staticaly linked component (rshmc804x_64.llb) that builds and work fine.

At the moment I load instrument (rshmc804x.fp file), and try to build it again, I get a lot of linker errors.

I found out that if I change the rshmc804x_64.llb to rshmc804x.llb (matching the prefix rshmc804x used in the FP file), it builds again OK.

The component also exists in 32-bit version (rshmc804x.llb), that is why the '_64' suffix is used for the 64-bit version to distinguish between them.

My question is: How do I get one FP file to work for both 32-bit and 64-bit versions, when they use different names for their llbs ?

Thanks,

Milo

[Constantin--P]

In order to use 32-bit lib on 32-bit configuration and 64-bit lib on 64-bit configurations follow the steps from this document:

Automatically Switching Between 32-Bit and 64-Bit Libraries in a LabWindows™/CVI™ Project

Constantin

[MM_RohdeSchwarz]

Hi ConstantinP,

thanks for the answer. Sorry I mixed up the file suffixes - lib / llb (I probably work too much with LabVIEW 🙂

However, the steps described work OK... until the point, you load the instrument's FP file (not just have it in the project, but have it loaded). Then, it only works if both lib have either the same name, or their name does not contain the name of the FP file.

Examples: FP file name is rshmc804x.fp

32-bit lib: rshmc804x.lib

64-bit lib: rshmc804x_64.lib

Not working

32-bit lib: rshmc804x_32.lib

64-bit lib: rshmc804x_64.lib

Not working

32-bit lib: Foo.lib

64-bit lib: Boo.lib

Working

32-bit lib: rshmc804x.lib

64-bit lib: rshmc804x.lib

Working

According the VXIpnp standard, the lib files must have different names for 32-bit and 64-bit, so I'd need the combination 1 or 2 to work 😞

Cheers

Milo