How to use system Clang instead of the bundled version
Prior to commit 97e9593070a80b408f7e87af2c277f7abf885d51 on 4.20 branch I was able to use whichever LLVM/Clang version I have installed on my system (e.g. 6.0.0, or 5.0.1) for building UE 4.20 and my own projects. That commits forces installation of a bundled Clang at version 5.0.0.
So, since I have third-party libraries built using Clang 6.0.0, is there any way to tell UBT to use a different Clang other than the bundled one, without reverting that commit or modifying the engine files?
asked Jun 28 '18 at 07:33 PM in C++ Programming
You can probably just create the Build/PerforceBuild.txt file
answered Jul 10 '18 at 09:25 AM
This might give you a hint:
UBT checks all possible clang shell commands and use first found on the list... so i guess simple solution is simply deleting clang in UE4 or simple don't path it in evrnament varables. "clang" will always be picked first so that one will be used with top proprity.
You can always modify UBT code if you like.
What linking issues are you running into when linking binaries built by clang 6 with binaries built by clang 5?
answered Jul 10 '18 at 01:41 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here