Recently I’ve worked on a project with a group of people, but currently after some commits the project will no longer compile in other machines. The error shows a series of header files that exist in the project, but with the older filepath. What’s odd is, the current file path seems to be updated correctly for everyone on the repo, as this was a very early name change.
We’ve already generated Visual Studio project files multiple times over, but it still won’t compile for them while my machine runes and compiles without issue.
Is their version of the project’s Build.cs file updated? I’ve been in situations where this file gets left out of commits, but it’s important for the project to find modules and header paths
I have found the issues and will list them out here.
-
MVCS: My collaborator was not using a VS version that had access to the minimum MVCS that allowed compiling UE5.7 projects. Updaing MVCS build tools to latest version
-
Diversion dv-conflict: Our project uses Diversion for repositories, and one of the features is the creation of backup files created when potential issues arise. Some of these files caused errors that stopped the solution from compiling.
-
bUseUnity: Just for safety, set the build.cs to bUseUnity = false
Doing all of this, the project compiled without issue.
