mass compile skips non-existent files

[bmann2000]

When mass compiling I am expecting either no log entry because everything is fine or Bad VI.

What I am experiencing is lots of "CompileFile: skipping".  The files mentioned no longer exist, but they were in the project previously.  How do I clean up the project to avoid receiving these mass compile log messages?

I have shown the file structure below to demonstrate that the files are not in the folder structure/project.  I am guessing the files were removed from the directory structure without the right-click remove-from-project being used in the project explorer window.

[crossrulz]

In the project Items view, the missing files should have a glyph showing an issue. Just use those to weed out the missing files.

[Kyle97330]

In the list of files, either right-click and select "Show in Items view" or press control-E.

That will take you to the other tab, with a good chance of being somewhere in the "Dependencies" list. 

If you're not in the dependencies list, just delete it from the project.

If you are in the dependencies list, right-click and select "Why is this item in Dependencies?" and you will either get taken to one item on the list if there's only one reason, or given a list of files if there's more than one.  If there's more than one, just pick the top one to start looking at.

You'll then need to open the file to find out what inside that file is pointing towards these not-on-disk files.  Most likely it will be something in a "Disable" structure of some other VI, and you will be able to remove them from your project by removing the disabled frame(s) from that structure. Could be other things too, but that's the most likely in my experience.

Resolve that, then go back to the next item in the files tab if there are any left.

[bmann2000]

Thanks for the suggestions.  The problem is the files listed in the mass compile log are "non-existent".

They do not exist in the project, in the dependencies, project view or files view, they are not there.

They are not in the directory structure when viewed with Windows Explorer.

They are listed by the massCompile log, but I cannot find any mention of them anywhere else.

The files did exist in the past, a long time ago, the Project is over 10-years old now and has been updated through several versions of LabVIEW.

[UliB]

---

@bmann2000 wrote:

Thanks for the suggestions.  The problem is the files listed in the mass compile log are "non-existent".

They do not exist in the project, in the dependencies, project view or files view, they are not there.

They are not in the directory structure when viewed with Windows Explorer.

They are listed by the massCompile log, but I cannot find any mention of them anywhere else.

The files did exist in the past, a long time ago, the Project is over 10-years old now and has been updated through several versions of LabVIEW.

---

Well, I don't know if this will be helpful, but I try.

- You mass compile a directory ( ...\RigOSv7production\Rig Operation ) 

- Mass Compile tries to find a file (e.g. ...\Examples\EpaqJoystick.vi) and skips it, because the file is not there / at the expected path.

Why is mass compile looking for EpaqJoystick.vi?

I say because there is a VI referencing EpaqJoystick.vi as SubVI and mass compile does not tell you which VI is referencing EpaqJoystick.vi. This VI does not have to be in your project, it only have to be within the specified directory. 

So my question is: Is there a VI within the specified directory or its subdirectories, which is not in your project and is referencing EpaqJoystick.vi? And I am not aware of an easy, one-click way in LabVIEW to get this VI, sorry.

I sometimes create a directory on disk called 'old' or 'unused' and fill it with -not used anymore- VIs, but they might reference VIs still in use or non-existing VIs.