I tried packaging my “C++ Basic Code” project for iOS (remote build using Windows 10 and OS X 10.11
). It failed and I notice the following line in the log which seems to be causing the problem:
UnrealBuildTool: ERROR: Couldn’t find required additional file to shadow: ThirdParty/libJPG/jpgd.cpp
, I can package a blank Blueprint project (no remote build as far as I know), but not a blank C++ project. What I did was just creating a C++ “Basic Code” template for “Mobile/Tablet”. I then setup the “[Remote Build Options][1]” and package for iOS and it gave me the mentioned error. No, I did not install libjpeg-dev. I cannot find anything concerning libjpeg-dev in the UE4 documentation. Can you give me some pointers about that? Thank you.
It’s been reported by other users within the community that when they installed the ‘libjpeg-dev’ it fixed the error for that. I would also try to re-verify your version of the engine, to make sure that there weren’t any files corrupted or missed during the installation process.
, I seem to be able to solve the problem without installing libjpeg-dev. I found the 2 files [jpgd.cpp and jpge.cpp][1] online, put them in \Epic Games\4.14\Engine\Source\ThirdParty\libJPG and the problem goes away. Are these 2 files supposed to be included in the current engine distribution?
Now, another problem appears during packaging which I am trying to solve:
UnrealBuildTool: Provisioning profile “iOS Team Provisioning Profile: *” is Xcode managed, but signing settings require a manually managed profile.
Thank you! I had the same issue in 4.15 and this solved it. I was going to submit a pull request with a fix for the engine but it looks like those source files are there in the Source version.
From looking at [this thread][1] it seems something in the BuildGraph isn’t picking up those files. I’m guessing a change to the CopyIOSFilter in InstalledEngineFilters.xml might do the trick:
``
But, actually building a binary release version of the engine from source is a pain (i.e. i ran into errors and am not going to bother because its undocumented). If there were instructions for that I could submit a pull request with a fix but as-is there’s no way for me to verify the change.