CVI-2009 Build Issues

[jcurl]

Hello,

I've installed now CVI-2009 (9.1.0 (427)) and I'm seeing some minor issues that make building the application a little tedious. Does anybody have any workarounds besides just clicking the menus manually?

1. When I do a batch build, it only builds the 32-bit variants. I'm trying to port my DLLs to 64-bit. Is there any way to get this to work? I'd especially find it useful to build both debug versions (I would call them testdll_dbg.dll and testdll64_dbg.dll) or my release dlls (testdll.dll and testdll64.dll).

2. When I do a build, it signs my debug application regardless of the option "sign if debug" is not checked. Is there any way to prevent this?

Thanks,

Jason.

[PeterAdelhardt]

Hi Jason,

thanks for your post!

1. This is a known issue and is documented as CAR #170375

2. Thanks for pointing us to that issue! It is documented as CAR #216375

You can always check with NI for the status of these issues. As always, you can see the list of fixed issues in the release notes of future versions.

Regards

[jcurl]

Something else I observed last night when building software for 32-bit and 64-bit that appears strange.

If I have an application that requires external libraries (e.g. mylib.lib/mylib.dll 32-bit and mylib64.lib/mylib64.dll 64-bit), if I build 32-bit, the linker should only depend on the 32-bit libraries. Indeed in the IDE it shows the 64-bit libraries as grey. However, if the 64-bit files are not available (in my case they were masked out by my view in ClearCase, but the 32-bit libraries were available), CVI 2009 could not link the final exe.

I had to explicitly remove the 64-bit libraries to compile 32-bit because the 64-bit libraries were not available.

Why when building 32-bit would CVI 2009 need to have the 64-bit files available?

[PeterAdelhardt]

Hi Jason,

we were not aware of the issue. Do you maybe have an example to demonstrate the problem?

Thanks

Peter