This means that iOS then fails to build.
This is similar to a similar problem where the default project location is under “Unreal Projects”
Showing Recent Messages
[178/179] sh /Users/thomasshepherd/MM 4.15/Binaries/IOS/MM_04-IOS-Shipping
clang: error: no such file or directory: '4.15/Binaries/IOS'
Steps to repro:
- From the engine project screen, open a project that is currently on a different engine version
- Choose Make A Copy
- Build for iOS
Sounds like a minor thing - but this means you have to rebuild the project files and then rebuild the project - which if you’re building from source takes a long time!
Hello theonecalledtom,
I tried reproducing this issue but I’m actually not failing, even with compiling with the project in the Unreal Projects folder. I did find a very old bug report that details the error with the space in the path itself but it is currently backlogged. This is the bug: UE-7164. Is it possible that this is specific to Source builds? I’m currently pulling 4.15 source on my Mac to test that but I was using Binary builds in particular originally.
Likely specific to source builds - this was one (happens to be the first I tried so I don’t have any comparison).
In this case you could change the code that generates a new name (actually would be very nice to be able to specify the name / location) to just use _s instead of spaces.
Hello theonecalledtom,
I apologize for the delay on this response; The fact that a space is generated when a copy of a project is made does not seem like a bug. The bug is that having a space causes problems on Mac in the first place. Please keep track of that particular bug for further information.