[CLion][Windows]build will hang on for 60 seconds before doing anything
I'm trying to replace Visual Studio with CLion for my development and I found build the "ProjectNameEditor" target with CLion is extremely slow than VS, and interesting thing is that the build will stuck for exactly 60 seconds before doing anything. This will be obviously if I change nothing and just hit the build button, it will stuck a minute and tells that:
But if I use Visual Studio, the build just go on when I hit the build button and it usually takes just few seconds.
What's more, if I change the code in CLion but compile it in the UE editor, it is fast.
And I found some video about using CLion, both of them takes 1 m xx s xx ms to build with a tiny change.
I got a intel i5 with 8GB memory and 256GB ssd, but I think this problem has nothing to do with the hardware, since Visual Studio build is fast.
So anybody knows why this happens?
I found a workaround using the new custom build targets in CLion version 2019.1. For a UE4 project, cmake eventually just runs Unreal's custom Build.sh script. So I configured a custom build target that invokes Build.sh directly. Follow the instructions in the CLion documentation to setup a custom build target. Here's a screenshot of my configuration:
This is working great! However, I discovered a bug: a custom tool fails to run if the tool has any whitespace in the path. For example, the default Unreal Engine installation resides in a directory named "Epic Games". Because of the space between "Epic" and "Games", the tool doesn't run. I worked around this by renaming the directory to "EpicGames" with no space. Would you like me to open a new ticket for this issue?
Follow this question
Once you sign in you will be able to subscribe for any updates here