CVI 2013 attempts to include 32-bit libraries in 64-bit project

[richferrara]

When attempting to build a project that can contain either 32-bit or 64-bit libraries, CVI 2013 incorrectly attempts to include 32-bit library files in a 64-bit build although the project window shows these files grayed out:

[Evan_S]

Hi,

I have a few questions which should help trouble shoot this. How are you including/not including the library in your current project? Have you used the process in earlier versions of CVI?

Also, have you tried automatically switching between versions of the library? There is an article posted here.

[richferrara]

We have all our library files in the same folder as our .prj and .cws files.  This has worked for us through CVI 2012.

I read the article you referenced.  Will that process work if the 32-bit and 64-bit versions of the library file have different names?

[Evan_S]

I believe that the process is for libraries of the same name, I had not noticed in your original post you already had the libraries named differently.

Could you walk me through the process you are using for including/not including the library in your current project?

[richferrara]

Evan,

We are storing all the library files (both 32-bit and 64-bit) in the same folder as the .cws and .prj files.  All the library files are included in the project -- LabWindows determines automatically which libraries to link into each type of project build.  It was doing this correctly through CVI 2012, enabling only the 32-bit libraries for 32-bit builds and only the 64-bit libraries for 64-bit builds.

Rich Ferrara