Jump to content

  • Log In with Google      Sign In   
  • Create Account

Interested in a FREE copy of HTML5 game maker Construct 2?

We'll be giving away three Personal Edition licences in next Tuesday's GDNet Direct email newsletter!

Sign up from the right-hand sidebar on our homepage and read Tuesday's newsletter for details!


We're also offering banner ads on our site from just $5! 1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


UE4 build tool


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
2 replies to this topic

#1 RobMaddison   Members   -  Reputation: 736

Like
0Likes
Like

Posted 04 May 2014 - 03:39 AM

Has anyone worked out UnrealEngine 4's build system yet?

The projects contain various different OS cpp files (iOS objective C files for example), and the build system doesn't attempt to build them (even though under win7 in the config properties 'build' is ticked under x64).

Also, when you build from clean, it appears to build and run the unreal build tool which is a dependency of the UE4 project - I can't see any post build steps in the config.

Thanks

Sponsor:

#2 SeanMiddleditch   Members   -  Reputation: 6355

Like
2Likes
Like

Posted 04 May 2014 - 10:49 AM

See things like UE4Game.Target.cs. You see sections like:

else if (Target.Platform == UnrealTargetPlatform.IOS)
{
	OutExtraModuleNames.Add("OnlineSubsystemFacebook");
	OutExtraModuleNames.Add("OnlineSubsystemIOS");
	OutExtraModuleNames.Add("IOSAdvertising");
}
The platform-specific code is usually in platform-specific modules, letting the top-level modules decide which sub-modules to build and link in.

Build properties of items in the IDE are essentially meaningless as they control behavior of MSBuild, which isn't being used. If you look at the project properties/configuration for the UE4 project you can see that its Configuration Type is "makefile". Clean/Build actions don't go through the standard Visual Studio process but rather completely through Epic's build tool via some batch files.

#3 RobMaddison   Members   -  Reputation: 736

Like
0Likes
Like

Posted 04 May 2014 - 12:21 PM

Ah, that makes sense - I did see makefile before but didn't realise the VS process wasn't being used at all.

 

Thanks






Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS