LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

labwindows CVI problem

Solved!
Go to solution

hello I´m trying to create an installer for an application created in a previous version of Labwindows CVI that a dont know becasuse i receive just de sources files, i´m working with 2010 version, the problem is that the application run perfect in debug mode but when i run it in release mode the application doesnt work, only the icon in the taskbar is showed but the graphic interface never appears, someone can help me with that

0 Kudos
Message 1 of 7
(3,993 Views)

Try to see if there are specific #ifdef in the source that may explain differences in compilation. Such as _CVI_DEBUG_. Otherwise you program may be buggy, with pointers initialised properly, by pure chance, in debug mode.

0 Kudos
Message 2 of 7
(3,978 Views)

I check all source files an there is no any  #ifdef that could cause problems, the program is correct because is running in an old PC, what i am doing is trying to create an installer to change the program to a new PC, what i receive was just the folders project that are in that machine, but i can do work the program in my machine.

0 Kudos
Message 3 of 7
(3,965 Views)

Does your program run in release mode in CVI (Ctrl-F5 after a complete compile, instead of Shift-F5) ? If so the problem must be in the configuration of the installer. See the details of the installer configuration. Are you including the runtime engine ?

0 Kudos
Message 4 of 7
(3,926 Views)

yes it is, i am not creating the installer because the program does not work in my PC, but the code is right because is working in the old PC, I have in the project dll´s and lib´s compiled in CVI 7.11 could be that the reason or is compatible with CVI 2010

0 Kudos
Message 5 of 7
(3,903 Views)

Try to recreate the export library from the dll

0 Kudos
Message 6 of 7
(3,889 Views)
Solution
Accepted by topic author maneqro

thanks for your help, the problem was not with the code, and was not with the RT Engine version, was a bad configuration in the release compilation configuration, I was not adding the externals dll´s and lib´s into the external modules option in target settings

 

0 Kudos
Message 7 of 7
(3,879 Views)