Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Rebuild entire engine after packaging


I am using a custom engine built from source with few bug fixes, and every time after I package my project I have to rebuild the entire engine in the Development Editor configuration. This can be very frustrating especially in a situation like now where I started the packaging process, cancelled because I forgot something and now have to wait 30-60 mins for it to compile... Trying to rebuild only the game project in Visual Studio doesn't work for me. Is that something that can be avoided or is there no way around it?


Product Version: UE 4.14
more ▼

asked Jan 18 '17 at 07:07 PM in C++ Programming

avatar image

457 36 33 54

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Hi Fluppi393,

To get an entire engine rebuild is not the intended workflow. If UnrealBuildTool decides to do a (re-)build, it must of detected some kind of (code or ini file) change. When the rebuild happens, do you see something similar to the following in your VS build output?

 2>  Creating makefile for {ProjectName}Editor (working set of source files changed)


more ▼

answered Jan 18 '17 at 07:46 PM

avatar image

1.7k 22 10 49

avatar image Matthew J Jan 18 '17 at 08:29 PM

Gheist is correct, it shouldn't require rebuilding the engine in any way unless changes are being made. You mention that you're forced to do so on Development every time you want to package... How exactly are you going about compiling that starts this? Are you hitting Build > Build Solution at the top of VS or using Ctrl+Shift+B? This option will build everything in the solution explorer and could result in this behavior. I would suggest right-clicking on your project directly and choosing build from the context menu. Also, the editor should actually never need to be built for "Development" and should only require either "Development Editor" or "Debug Editor" for most situations.

avatar image Fluppi393 Jan 18 '17 at 08:54 PM

Sorry I think I am mixing some things up here, I am a bit confused because at times the engine rebuild seems pretty random to me. So here is exactly what happened: -Built the project in Development Editor -Started and cancelled packaging -Changed to Development Game configuration -Build project by clicking on "Local Windows Debugger" (which should as of my knowledge only build out of date projects)

Then the process as in my post above began, taking about 20-30 minutes. After that I switched to Development Editor and compiled it without problems, then back to Development Game and had to do the same thing again. I am pretty sure that usually doesn't happen when switching between these two modes.

avatar image Matthew J Jan 24 '17 at 09:15 PM

For some reason, Visual Studio prompts for building everything involved when you go to launch the editor in debug. If you know that your project is up to date, you can feel free to hit "No" when prompted and no building should occur.

avatar image Fluppi393 Jan 18 '17 at 08:31 PM

Thanks for the quick reply, I may have spoken too soon it is not actually rebuilding the entire engine, but doing this: 1>------ Build started: Project: ShaderCompileWorker, Configuration: Development_Program x64 ------ 1> Target is up to date 2>------ Build started: Project: BrickRigs, Configuration: Development_Game x64 ------ 2> Performing full C++ include scan (building a new target) 2> Creating makefile for BrickRigs (UnrealBuildTool.exe is newer) 2> Building UnrealHeaderTool... 2> Target is up to date 2> Parsing headers for BrickRigs 2> Running UnrealHeaderTool "D:\Unreal Projects\BrickRigs\BrickRigs.uproject" "D:\Unreal Projects\BrickRigs\Intermediate\Build\Win64\BrickRigs\Development\BrickRigs.uhtmanifest" -LogCmds="loginit warning, logexit warning, logdatabase error" -Unattended -WarningsAsErrors 2> Reflection code generated for BrickRigs in 27.9298939 seconds 2> Performing 305 actions (4 in parallel) 2> PCH.CoreUObject.h.cpp 2> PCH.Core.h.cpp 2> PCH.EnginePrivate.h.cpp ...

avatar image Ciprian Stanciu Apr 03 '19 at 05:08 PM

It's probably not the entire engine but a heavy chunk of it. I think this situation is due to the fact that the C# configuration project ( the one that uses your Project.target.cs) for each module needs to be rebuilt because if you look at the binaries, there's no Debug/Development version of the DLLs, just a single version, so changing configurations between Debug/Development/Shipping triggers recompilation.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question