[Fix inside] Since 4.13.x compilation fails due to source code glitch

Hello,

4.13, 4.13.1 and 4.13.2 all introduce a bug which makes my project impossible to compile.

It’s the file EdGraphToken.h which is missing include:

#include "EdGraph/EdGraphPin.h"

Is it something with my build, or is it a general oversight?

I can easily fix it by adding this include into “4.13\Engine\Source\Editor\UnrealEd\Public\EdGraphToken.h”
but I have to do it always after upgrading the version.

Is there anything I am missing?

Thanks,
Jan

Hello metamorphium,

As no one else has reported this error and we’ve not seen anything wrong with it internally, this may be something related to the project you’re using. If you download a new version of the engine (I’m assuming you’re getting all of your builds from Github?), when do you receive a compilation error? Is it when you’re compiling the engine or when you’re trying to compile your project? What is the exact error? When you download the engine, are you overwriting a previous installation or placing it in a new directory, running setup.bat, and generating project files as suggested?

If this is only blocking your project from compiling, can you try adding that include to your project’s projectnamehere.h file instead of editing the source to see if that works?

Hi Matthew,

thank you for getting back to me. I don’t use github sources, only those, which launcher downloads upon upgrading, so I believe it is the preferrerd way?

My workflow is that I upgrade the engine, then I rightclick on project file and generate project files, then it recompiles and with every 4.13.x it fails like this. I do this like that since 4.6 and the glitch appeared only in 4.13.

I can try adding this file into my projectname.h, but I am not sure how this could help since EdGraphPin class and EdGraphToken.h are both deep in the engine itself and obviously EdGraphToken is simply not referenced in the said file.

I will try anyway.
Thanks!
Jan

We haven’t heard from you in a while, matemorphium, Did you ever get to try what I suggested? If so, what were the results? Are you still experiencing this issue? In the meantime, I’ll be marking this as resolved for tracking purposes.

Hi Matthew,

I’ve upgraded to 4.14 and the problem went away.

Thanks,
Jan