Closed meetakshay99 closed 3 years ago
I didn't notice the segfault but have the same problem with "ue4 build" with ubuntu 20.10.
If the engine components (namely the ShaderCompileWorker) are already built from source you can use the "-notools" flag as temporary work-around. This omits the check and build of ShaderCompileWorker.
$ ue4 build -notools
Whoops, my bad!
This is fixed in https://github.com/adamrehn/ue4cli/commit/72146610532d5e9dea6368f84b8a86138cf64319, which is now live in ue4cli version 0.0.50. Apologies for that silly oversight, evidently I didn't test the ue4 build
command for regressions when I implemented the ue4 build-target command the other day.
@meetakshay99 I'm not sure what's going on with regards to that segmentation fault, but I have to assume it's something related to pip itself given that the packages all appear to install correctly.
Installing ue4cli and conan-ue4cli on linux host prints "Segmentation Fault" at the end. Then I ran commands "ue4 setroot" and "ue4 conan generate" and they succeeded. But when I tried to build the app "ue4 build", it failed. "ue4 build" works for 4.26 in a container. This issue happened on linux host. Below is the complete log showing all the above-mentioned commands being performed: