Filename too long in build

[WindNRG]

I agree this is a bug. I don't like changing my directory structures to accommodate this. Does anyone know what the difference in functionality is between the new build method as opposed to the 8.x method of using an LLB. How will I be affected?

[WindNRG]

Also, why was this changed? What was the problem with the 8.x one?

[tst]

I assume that the main reason it was changed was classes. One of the key features of classes involves having different VIs with the same name. Since a single folder can't have two files with the same name, LV 8.2-8.6 had to save the duplicate files outside the EXE. LV 2009 solved this by maintaining the full hierarchy inside the EXE.

The only differences in functionality are probably that in 8.x you have to copy more files (if you have classes with duplicate VIs) and that if you strip and build paths, you may have to account for the different structure.

[crelf]

It's still a bug in my opinion...

[WindNRG]

Ok, I understand why, and it is benificial to have this new feature, but it still should not limit where I put my build directory and how I structure my projects folder.

[shew82]

Yeah - the 2009+ layout is really useful but this error is something that could be easily caught and simply handled (even if LV simply has a build cache folder close to root, etc) - as such, I'm with you, this is something that definaltely be fixed/changed.

[tst]

It should probably also be pointed out that you can probably run into this even after you build the EXE. I wouldn't be surprised if you would also get an error if you install and then run it from a location which makes the eventual path too long. Which isn't to say this is good behavior.

[crelf]

---

@tst wrote:

It should probably also be pointed out that you can probably run into this even after you build the EXE. I wouldn't be surprised if you would also get an error if you install and then run it from a location which makes the eventual path too long. Which isn't to say this is good behavior.

---

True, but that's something I think is more on the onus of the developer to try to limit (albeit impossible to force, since we have to let the installer person choose where to put the default directory - limiting *that* sounds like a good new idea for the idea exchange...), whereas the issue we're talking about is a flat-out LabVIEW bug.

[altenbach]

So, I just got stung with this building my application (which always worked before):

---

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

Error 6 occurred at AB_Destination.lvclass:Create_Destination.vi -> AB_Build.lvclass:Create_Destinations.vi -> AB_Build.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW: Generic file I/O error.

---

(No other information. This is in Windows 7 64 bit, LabVIEW 2011 SP1) What's the best way to find the file that is too long??)

[altenbach]

Solved it. The last subVI that I made had a filename of 54 characters (without extension). after shortening it, everything worked. 😄