LabVIEW 8.6 Build Ends Immediately With No Executable

[Mr._Jim]

Hi All,

In reading the subject line, I'm going to venture that many of you are probably thinking I goofed up my build spec, but I don't think I did. :smileywink:  (I'll be really embarrassed if that's the case)

I just opened a LabVIEW 8.5.1 project in 8.6, made some changes, and then tried to run my build spec to generate an executable. Mind you, it worked perfectly for months in 8.5.1, I I know full well that this doesn't mean it will work now. The build immediately finished with no special message, producing no executable.  (see attached dialog)  I figured that it was some fluke in converting to 8.6, so I tried the following:

1. Double, triple, and quadruple checking my build specification to make sure I didn't goof up somewhere

2. Started over and made a new build specification (just like the good old days when the builds in 7.x and earlier failed)

3. Moved the build folder out of my auto-populating hierarchy.  I thought for sure that would be the problem, but it didn't fix it.

4. Mass compiled the project hierarchy, thinking that if the build detects changes it'll start from scratch.  (Nothing.)

No matter what I do, I get the attached dialog immediately and nothing happens. Has anyone seen this?  Is there something silly I missed?

Thanks a lot,

Jim

[Mr._Jim · Accepted solution]

Okay, so after some trial and error I managed to get past this...  It seems like LabVIEW has some sort of cache for names of executables generated by build specifications.  I renamed my executable and it started to build normally...  Even if I moved the destination for the executable, it still wouldn't build, but renaming the executable itself fixed it.  Very strange; I've never run into this before.

[Rocket Girl]

I am having the same problem.  My build is looking for applications to add to the build from disk 1 and disk 3 of the Aug 2008 version.  I put in my DVD and it can't find the files. Is disk 1 a CD disk or a DVD disk?  What are the correct paths for the build to find the applications to include with the build?

[Mr._Jim]

Hi Rocket Girl,

I don't think this is the same problem, but nonetheless... Generally if LabVIEW is asking for things to add to builds, they're off the driver CD's.  Previously the driver CD's were included as actual CD's, but in the August 2008 edition they're in DVD4 under "DCD-Aug-08-#", where # is the CD number.  (DCD 1 doesn't exist - it's not just you)

Jim

[Rocket Girl]

Yes, I agree your cache problem is different.  Thanks for the input.  I was able to direct the build to the correct DVD's.  Thanks,

[Mr._Jim]

No problem... Glad to help!