jgcode Posted August 26, 2009 Report Share Posted August 26, 2009 (edited) [Cross Posted to NI] I made a post in this topic regarding build errors in LabVIEW 2009. After thinking about it a bit more I thought it may be worth a topic. I had some code that worked fine on my home PC, when I moved it to work, the exe would not build due to errors. The errors coming back weren't that good at explaining the problem Until I got this one: Look at the path in the error: C:\Users\Developer2\Desktop\User Group Meeting\LabVIEW 2009 new features\code\02 intermediate\01 build specifications\build executable file paths\dist\application 9.0\my application.exe\LabVIEW 2009\vi.lib\addons\_ICON Library\String\_icon_lib_string.llb That path is referring to a VI inside my executable! This may be a bigger issue that I first thought So my question is: If a have a path inside my build that would be relative to the executable and LabVIEW needs to resolve it, could that process fail depending on where the exe sits in a folder hierarchy? I guess this could have happened before? but it would be more likely now due longer paths! Edited August 26, 2009 by jgcode Quote Link to comment
jgcode Posted August 26, 2009 Author Report Share Posted August 26, 2009 (edited) Answers posted by Gmart in original topic: Edited August 26, 2009 by jgcode Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.