LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

cvi 2013 does not create exe

Solved!
Go to solution

Hi all!

 

While CVI 2013 works fine on my desktop machine, on my laptop computer it does not compile nor build any exe file. When I use Build>>Rebuild it just tells me

"Failed to copy c:\...\Debug\...exe to c:\....exe. File not found.

CVI 2012 on the same machine works fine.

 

Anyone any idea?

 

Kind regards,

Thomas

0 Kudos
Message 1 of 7
(4,649 Views)
Solution
Accepted by topic author Thosch

Just a hunch that some paths may be wrong on your laptop. Open the .prj file in a editor and take a look at the various Path variables, see if anything points to absolute directories that don't exist.

0 Kudos
Message 2 of 7
(4,639 Views)

Arghh, stupid! Of couse that was problem.

But it follows the question: Why the project file must contain absolute paths?

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

As a general rule, the project file contains absolute paths only if it can't build a relative path between the file in question and the folder where the project is saved, or some other reference folder in your computer (e.g. the CVI installation root folder). Typically, this would only happen if those files are in a different drive. Is that what happened in your case?

 

Luis

 

 

0 Kudos
Message 4 of 7
(4,614 Views)

Yes, the CVI root folder is on a different drive. But why needs the project file the absolute path to CVI? Couldn't CVI get the path from Windows registry?

 

Thomas

0 Kudos
Message 5 of 7
(4,607 Views)

The answer depends on the function of the path that was saved as an absolute path. There are many paths in a project file, and ni order to try to figure out the reason why it was saved as an absolute path I need to know which of those paths this one is. I don't know if it corresponds to one of the files in your project or if it's some other path that corresponds to some project setting.

 

If you open the .prj file that was saved in your desktop computer in a text editor and search for the absolute path in question, can you let me know what is the full name of the tag in question, and what section of the .prj file that tag is in? You don't have to send me the actual path, by the way. Just the text to the left of the = sign.

0 Kudos
Message 6 of 7
(4,598 Views)

hello me have same problem with debug mode, can't create exe file, but in release mode everything work fine.

 

what it can be, i checked all the paths absolute and relative,

and another issue, i can't activate build output window (it's in gray color )

 

i don't know that to do.

 

my .prj file:

 

[Project Header]
Version = 1201
Pathname = "/c/Users/Public/Documents/National Instruments/CVI2012/samples/sett/sett.prj"
CVI Dir = "/c/program files (x86)/national instruments/cvi2012"
CVI Shared Dir = "/C/Program Files (x86)/National Instruments/Shared/CVI"
CVI Pub Local Dir = "/C/ProgramData/National Instruments/CVI2012"
CVI Pub Global Dir = "/C/ProgramData/National Instruments/CVI"
IVI Standard Root Dir = "/C/Program Files (x86)/IVI Foundation/IVI"
VXIplug&play Framework Dir = "/C/Program Files (x86)/IVI Foundation/VISA/winnt"
IVI Standard Root 64-bit Dir = "/C/Program Files/IVI Foundation/IVI"
VXIplug&play Framework 64-bit Dir = "/C/Program Files/IVI Foundation/VISA/win64"
Number of Files = 1
Target Type = "Executable"
Flags = 2064
Copied From Locked InstrDrv Directory = False
Copied from VXIPNP Directory = False
Locked InstrDrv Name = ""
Don't Display Deploy InstrDrv Dialog = False

[File 0001]
File Type = "CSource"
Res Id = 1
Path Is Rel = True
Path Rel To = "Project"
Path Rel Path = "sett.c"
Path = "/c/Users/Public/Documents/National Instruments/CVI2012/samples/sett/sett.c"
Exclude = False
Compile Into Object File = False
Project Flags = 0
Folder = "Source Files"

 


[Create Executable]
Executable File_Debug Is Rel = True
Executable File_Debug Rel To = "Project"
Executable File_Debug Rel Path = "sett_debug.exe"
Executable File_Debug Line0001 = "/c/Users/Public/Documents/National Instruments/CVI2012/samples/sett/sett_debug.e"
Executable File_Debug Line0002 = "xe"
Executable File_Release Is Rel = True
Executable File_Release Rel To = "Project"
Executable File_Release Rel Path = "sett.exe"
Executable File_Release = "/c/Users/Public/Documents/National Instruments/CVI2012/samples/sett/sett.exe"
Executable File_Debug64 Is Rel = True
Executable File_Debug64 Rel To = "Project"
Executable File_Debug64 Rel Path = "sett.exe"
Executable File_Debug64 = "/c/Users/Public/Documents/National Instruments/CVI2012/samples/sett/sett.exe"
Executable File_Release64 Is Rel = True
Executable File_Release64 Rel To = "Project"
Executable File_Release64 Rel Path = "sett.exe"
Executable File_Release64 = "/c/Users/Public/Documents/National Instruments/CVI2012/samples/sett/sett.exe"
Icon File Is Rel = False
Icon File = ""
Application Title = ""
DLL Exports = "Include File Symbols"
DLL Import Library Choice = "Gen Lib For Current Mode"
Use IVI Subdirectories for Import Libraries = False
Use VXIPNP Subdirectories for Import Libraries = False
Use Dflt Import Lib Base Name = True
Where to Copy DLL = "Do not copy"
Custom Directory to Copy DLL Is Rel = False
Custom Directory to Copy DLL = ""
Generate Source Documentation = "None"
Add Type Lib To DLL = False
Include Type Lib Help Links = False
TLB Help Style = "HLP"
Type Lib FP File Is Rel = False
Type Lib FP File = ""
Type Lib Guid = ""
Runtime Support = "Full Runtime Support"
Instrument Driver Support Only = False
Embed Project .UIRs = False
Generate Map File = False

 

0 Kudos
Message 7 of 7
(4,456 Views)