I would assume that something inside the *Target.cs or *.Build.cs files that control the unreal build tool has changed from beta to the current version.
Maybe there are differences between your ExilEditor.target.cs and the *Target.cs files that ship with the engine that indicate the error?
"C:\GitHub\UnrealEngine\Engine\Build\BatchFiles\Build.bat" UE4Game Win64 Development
This worked, it recompiled the full engine. So my thought here is that calling the UnrealBuildTool with a target that doesn’t exists locally produce an error. I have no idea why during the Rocket Beta it was working globally and not now anymore…
Or maybe it’s because I use the engine version I compiled myself ?
The only other thing I can think of is t try running the UnrealBuildTool from the Unreal Engine directory.
This is how I have it setup in the batch file:
echo Switching to Unreal Engine directory...
pushd "C:\Program Files\Unreal Engine\4.0"
echo Now in "%CD%"
if not exist .\Engine\Binaries\DotNET\UnrealBuildTool.exe goto Error_NoUnrealBuildTool
echo Running UnrealBuildTool...
.\Engine\Binaries\DotNET\UnrealBuildTool.exe %PROJECT_NAME%Editor Win64 Development "%PROJECT_DIR%\%PROJECT_FILE%" -rocket
popd
goto Check_Compile_Error
This definitely works with a the binary build of Unreal Engine 4.
Not sure if it will work with a custom build.
I’ll have to try it myself.
Converting this to a comment since it didn’t answer it for you (yet).
I just tried that and it still doesn’t work. I switched to the binary build too just in case. I still get the same problem. It’s like the compiler can’t find my “ExilEditor.Target.cs” which is properly defined inside the “Intermediate\Build\BuildRules\ExilEditorModuleRulesSourceFiles.txt”. :\
I copied the line from the NMake settings of my Visual Studios project, so I can’t see why I would have made a mistake like that (which was what Epic Games developers recommended me during the Beta). By the way, your suggestion doesn’t work, the configuration name is not recognized at all.
It does appear that your project files are stale. Since you upgraded have you had a chance to regenerate the project files. ExilEditor, unless you specifically named your project that, should not exist. instead you should have one project file for your game, and separate configurations.
In my case, I have
Solution ‘UE4’
->Engine
->->UE4
->Games
->->MyGame
and in configurations i have
Development
Development Client
Development Editor
Development Server
Ah, please ignore my previous comment. I overlooked that you had Unreal Build Tool in your command.
I have just attempted to repro your issue on my end and found it was successful.
D:\GitHub\UnrealEngine\Engine\Binaries\DotNET>UnrealBuildTool.exe HurlGameEditor Win64 Development “D:\GitHub\UnrealEngine\HurlGame”
Target is up to date.
I was just able to repro by altering the path of the uproject,
D:\GitHub\UnrealEngine\Engine\Binaries\DotNET>UnrealBuildTool.exe HurlGameEditor Win64 Development "D:\GitHub\UnrealEngine\HurlGame"
ERROR: Couldn’t find target rules file for target ‘HurlGameEditor’ in rules assembly ‘HurlGameEditorModuleRules, Version=0.0.0.0, Culture=neutral, PublicKeyToke
n=null’.
[…]
Vs
D:\GitHub\UnrealEngine\Engine\Binaries\DotNET>UnrealBuildTool.exe HurlGameEditor Win64 Development "D:\GitHub\UnrealEngine\HurlGame\HurlGame.uproject"
Target is up to date.
It may be worth verifying your uproject filepath:
“V:\UE4Projects\Exil.uproject”
"path\to\BatchFiles\Build.bat" "MyUProjectEditor" Win64 Development -WarningsAsErrors "path\to\MyUProject.uproject"
Note that you have to attach “Editor” suffix to first argument. The build.bat available in BatchFiles folder calles UnrealHeaderTool. Arguments must be in this exact order.
