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"

[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: NoActionsToExecute executor: 0.00 seconds

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?

Product Version: UE 4.21
more ▼

asked Jan 15 '19 at 04:30 PM in C++ Programming

avatar image

11 1 1

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

1 answer: sort voted first

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:

CLion Custom Build Target 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?

more ▼

answered Apr 09 '19 at 07:56 PM

avatar image

Dsmith Ws
1 1 1

avatar image Dsmith Ws Apr 10 '19 at 01:08 PM

Disregard the last sentence where I ask if I should "open a new ticket". That was pasted from an email to JetBrains, but I can't seem to edit my post here.

(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