Xcode project in 4.8

Development Platform & Builds
, , , ,
1

This is more of a regression or rather a feature request for OS X / Xcode. In 4.7 the engine source was part of the Xcode project, but it is no longer part of projects generated in 4.8. Having the engine source as part of the Xcode project was very convenient because you could just command + click on any of the engine provided class methods/functions and jump directly to their definition and read actual source code and how they are implemented.

Having that is huge, at least for me, when developing and learning the engine in general.

Having the engine sources as part of the Xcode project files might be scary to people, but they can be part of the project file and not associated to any compile target and as such they’ll never compile, or, worse case, associated to some dummy target.

My current solution is to manually add the engine source to the Xcode project, but it would be nice if that was done by default, especially since "it used to work"™

2

Hey dudrenov -

Thanks for reporting this, I was able to reproduce and have entered it in as UE-17090.

I’ve also gone ahead and updated our test case to make sure we’re covering this scenario.

3

Hi, I also want to have that fancy feature again.
Do I only need to link the Engine Source Files in the project without adding it to any target and Xcode will find the definitions for me?
Thanks.

4

Hi, it should, once Xcode is done indexing them. But it’s a futile effort over all. Coz’ every time you regenerate the project file you have to re-add them, which ends up being very annoying in the long term.

5

Just for an update this issue has been fixed for 4.9.0 and is in Preview 1.

6

That’s great! Thank you guys!