4.19 usage on windows

[SkaveRat]

How should I set up the integration on windows?

I've migrated a project from .18 to .19 and changed the editor in the settings.

There is no CMakeList generation anymore, which causes the current file to reference old .18 paths. Replacing all .18 path with .19 doesn't seem to work, at it can't find the Intermediate/ProjectFiles/ files anymore.

Recompiling inside the editor didn't anything, so I'm not really sure what to do next. Any ideas?

[TomCoursow]

Same here...
I can click Generate CMake Project after selecting CLion as Code Editor in the Settings but there is no File generated...

I saw that the UE4 Repo has some Pull Requests to fix these issues but they are not yet accepted right now.
https://github.com/EpicGames/UnrealEngine/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+clion

[reapazor]

So there is a bug 'higher up' in UE that was introduced in 4.19 that doesnt allow non native source code accessors to be used properly (so vs on windows, xcode on mac). This has bee resolved in source builds, just gotta hold tight unfortunately till it is released.

[SkaveRat]

Any workarounds until the 4.19.2 release?

[SkaveRat]

I just checked out the current 4.19 head (a599ee9) and the cmake file still isn't updated

[reapazor]

Hmm maybe it hasn’t been brought over yet, I’ll double check master tomorrow. I put a quick hack up a while ago as a quick change to make it work against 4.19 … I’ll dig that up too.

…

-- Matthew Davey dotBunny From: SkaveRat <notifications@github.com> Reply-To: dotBunny/CLionSourceCodeAccess <reply@reply.github.com> Date: Tuesday, April 24, 2018 at 18:35 To: dotBunny/CLionSourceCodeAccess <CLionSourceCodeAccess@noreply.github.com> Cc: Matthew Davey <matthew.davey@dotbunny.com>, Comment <comment@noreply.github.com> Subject: Re: [dotBunny/CLionSourceCodeAccess] 4.19 usage on windows (#99) I just checked out the current 4.19 head (a599ee9) and the cmake file still isn't updated — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#99 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAGD3E3sAWOpj9ajfZzheb81A1PxdMmNks5tr6iRgaJpZM4TZDqY>.

[SkaveRat]

And as suspected, 4.19.2 didn't fix the issue

[reapazor]

I know ☹ Im on it.

…

-- Matthew Davey dotBunny From: SkaveRat <notifications@github.com> Reply-To: dotBunny/CLionSourceCodeAccess <reply@reply.github.com> Date: Tuesday, May 1, 2018 at 13:35 To: dotBunny/CLionSourceCodeAccess <CLionSourceCodeAccess@noreply.github.com> Cc: Matthew Davey <matthew.davey@dotbunny.com>, Comment <comment@noreply.github.com> Subject: Re: [dotBunny/CLionSourceCodeAccess] 4.19 usage on windows (#99) And as suspected, 4.19.2 didn't fix the issue — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#99 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAGD3P53ycD_Y4PKkavIntR3T3yn7W9Iks5tuJzCgaJpZM4TZDqY>.

[Brainshack]

I tried it with current github master and while it generates the CMakeLists.txt file now, I get an error:

"Cannot load settings from file '....MyProject.idea\misc.xml' Error on line 1: Content is not allowed in prolog. Please correct the file for content.

Here is the content of that file. It looks fine to me.

<project version="4">
	<component name="CMakeWorkspace" PROJECT_DIR="$PROJECT_DIR$" />
	<component name="CidrRootsConfiguration">
		<excludeRoots>
			<file path="$PROJECT_DIR$/Binaries" />
			<file path="$PROJECT_DIR$/Build" />
			<file path="$PROJECT_DIR$/Content" />
			<file path="$PROJECT_DIR$/DataTables" />
			<file path="$PROJECT_DIR$/DerivedDataCache" />
			<file path="$PROJECT_DIR$/FeaturePacks" />
			<file path="$PROJECT_DIR$/Intermediate" />
			<file path="$PROJECT_DIR$/LocalBuilds" />
			<file path="$PROJECT_DIR$/Samples" />
			<file path="$PROJECT_DIR$/Saved" />
			<file path="$PROJECT_DIR$/Templates" />

			<file path="$PROJECT_DIR$/Engine/Binaries" />
			<file path="$PROJECT_DIR$/Engine/Build" />
			<file path="$PROJECT_DIR$/Engine/Content" />
			<file path="$PROJECT_DIR$/Engine/DerivedDataCache" />
			<file path="$PROJECT_DIR$/Engine/Documentation" />
			<file path="$PROJECT_DIR$/Engine/Extras" />
			<file path="$PROJECT_DIR$/Engine/Intermediate" />
			<file path="$PROJECT_DIR$/Engine/Programs" />
			<file path="$PROJECT_DIR$/Engine/Saved" />
		</excludeRoots>
	</component>
</project>

[Sygan]

I was successful with generating CMakeLists.txt from UnrealBuildTarget.exe. I had to replace all '' in file names to '/' in order to make it to work.

I also got @Brainshack information but it is a IntelliJ warning not an error so I think it is safe to ignore it for now.

I got this when CMake was loading, any ideas?

This is a very long error. I've put it on gist here if anybody cares to look at it:
https://gist.github.com/Sygan/a51f31b11ed12450cd91c577b6e717f3

[AlexisWeil]

@Sygan same problem. I haven't tried it for now, but I read that if you build UE 4.19 directly from sources, it could fix this problem.

I may try this today, I'll keep in touch with you if it works.

[reapazor]

I realize how much this sucks :(
Epic has promised to resolve a problem internally "higher up" for 4.20.

[SkaveRat]

is there a ticket opened about it somewhere that can be followed?

[reapazor]

That's part of the problem, there isn't a public discussion about it. Effectively non native project types dont generate properly in 4.19, it was a late introduced bug in the build system.

[Sygan]

@Zarkus13 I've also found this information, so I tried to build it from sources - I'm a novice to UE4 so it took me a moment to get it right.

I had some problems with missing files (because I've deleted the retail version) so I did some digging and found two pull requests fixing the issue with generating CMakeLists. I've implemented them (to master branch) and although I was able to generate the file, the g++ error persisted.

I also noticed that the version I've built (with modifications) didn't get the CLion from Code Editor in UE4 Settings. I had to manually tell it in code to use CLion because it has always fallen back to VS.

But as I said I'm no expert in UE4 so I could did something wrong and if you could confirm that GitHub version of the engine doesn't fix this issue then I would be glad.

[Sygan]

All right, I was somewhat successful :)

When I had g++ error at first time I've also tried to change toolchain in CLion to MSVC compiler but it also gave me an error.

After everything from above I thought that maybe the problem is not in Unreal but it lies somewhere in g++ or CLion. So I've downloaded CMake from the web and run it manually. By default it used MSVC and it had finished with success. Then I've changed CLion built-in CMake to the one I've downloaded and although it failed with the g++ error again it had no problems when I've changed the compiler to MSVC.

At this point CLion had indexed all of the files properly and it works fine. You can't use debugging with MSVS in CLion though...

So right now I see two possible issues why g++ failed.

1. Maybe it's g++ version issue and it might be good to check it with some other versions.
2. There might be something in g++ command that makes it crash but is accepted just fine by MSVC.

I still need to investigate this further. There is too many things I've did so I need to take few steps back and check what really "fixed" the issue and try to make g++ working (because breakpoints are nice)