LabVIEW
LV executable gets renamed with the word conflict
Solved!
Is your target destination monitored by a tool such as Google drive, OneDrive, or similar?
A builder typically makes a temporary gigantic mess and these file monitoring tools can be thrown off track or even crash as a result.
The renaming is most likely done by something external to LabVIEW. Make sure you are building to a local plain folder.
@N2STC wrote:
You are correct. When I build to a folder on my hard drive it's fine. The original destination was a network folder handled by Synology. Interestingly, when I copy the local one over to the network location, no renaming occurs.
Yes, as simple copy is a clean operation.
If you open the local folder while the build happens, you'll notice lots of "odd activity" (files/folders appearing/disappearing, etc.). In the long run LabVIEW should maybe change the way things are built. For example, all the temporary work could be done in the local TMP folder, followed by a move of the complete build to the final destination. Not sure what that change would involve.
