Linking Static Libraries Using The Build System - Epic Wiki
# Linking Static Libraries Using The Build System
From Epic Wiki
Jump to: navigation, search
# Contents
- 1 Overview
- 2 Visual Studio 2013/2015 - Library Configuration
- 3 UE4 - Build System
- 4 Visual Studio 2013/2015 - Linking Our Library
- 5 More Information
# Overview
The goal of this tutorial is to show you how to link a static library into UE4 using the Build System. This is primarily targeted at developers that are not intending to make engine level modification, but still want to extend the capabilities of UE4 with a library that provides such capabilities.
For examples sake, I will be creating a library called BobsMagic and linking into a UE4 project called UE4Magic.
# Scope & Notes
- You will be able to link in a library of your own design by the end
- I will not go too deeply into exposing functions or defining any API
- I expect you to have, at the very least, a more than cursory level of knowledge about C++, C# and MS Visual Studio 2013
- All Code paths provided are from the UE4 Project's base directory.
# Visual Studio 2013/2015 - Library Configuration
It is important that you compile out your static libraries with the same version of MS Visual Studio as you are using to work with UE4. This is because each edition of Visual Studio comes with a different compiler, leading to incompatibilities in the binaries. Rest assured if you cross into this realm you will get a warning when you attempt to compile the library in.
# Creating the project
Please go to the MSDN and follow the steps there in order to create a new Static library. Once you have finished, please return, as we have to make a couple of modifications to be able to get things working.
# Updating another Project
When you open up a project with Project or solution files targeted at an earlier edition of Visual Studio you are asked to upgrade. Allowing this to proceed will address the point at the beginning of this section. If you missed that dialog, or by chance it was not shown to you, it is possible to upgrade by going to the menu bar Project > Update VC++ project when it is selected in your solution explorer.
# Customizations for Targeting UE4 Modules
We will need to make a few other modifications to ensure that our libraries are able to be linked in easily.
# Targeting 64 bit platforms
With a standard Static Library project we will be targeting x86 (32 bit) machines, which wont work for the UE4 toolset.
- Open the Project Properties page.
- Choose Configuration Manager
- Open the Active Solution Platform drop down list and select <New...>
- Type in or select x64 if it is there
- Save it by clicking OK
You should be able to close out your project at this point. You should see it in the drop down at the top of Visual Studio.
# Multi Threaded DLL
The unreal build system expects you to be providing a static library that is then linked into a DLL, so we have to ensure that our project does this as well.
- Open the Project Properties Page
- Filter through to Configuration Properties > C/C++ > Code Generation > Runtime Library
- From the drop down list select Multi-threaded DLL (/MD)
- Save it by clicking OK
# Third Party Directory
sample directory layout
Build your project and note the location that the libraries are output to. Your lib file(s) should be in /bin/Debug or /bin/Release depending on the mode you built your project with, unless you changed them before hand. We will be moving them from here into our UE4 project directory, for ease of reference and later packaging.
Open up a new explorer window and navigate to your Project directory. Once there, create a new path for your library - /ThirdParty/BobsMagic
You will want to follow this step for each library you wish to reference, if I were to be adding in the V8 library I would create /ThirdParty/V8
Within this directory we will be adding two new folders - Libraries and Includes - to house their respective files. Includes are the header files that come with your library, used to define the API (Application Programming Interface) for you to reference in UE4. You should copy your *.lib file(s) into the Libraries directory.
Note: This is an arbitrary directory. It is only important to note its path so you can reference it in the build system later.
# UE4 - Build System
Now we are going to step into the UnrealEngine and actually address the binding of our library to the engine.
The build system requires some C# code, but you shouldn't fret. Our example is going to be pretty simple and so you should be alright to copy and paste the majority of the following code.
# Extending the Base ModuleRules class
For anyone doing this as more than a one off you can, and probably should, add in a couple of properties to the ModuleRules class. The two I will be noting here are convenience properties to ensure that we always know where our Module and ThirdParty directories are. These two properties will leverage the System.IO namespace, to utilize a couple of the Path static methods.
inside /Source/UE4Magic/UE4Magic.Build.cs
public class UE4Magic : ModuleRules {
private string ModulePath { get { return ModuleDirectory; } }
private string ThirdPartyPath { get { return Path.GetFullPath( Path.Combine( ModulePath, "../../ThirdParty/" ) ); } }
[Constructor]
}
# Loading Our Libraries
Next we will dive into our modules constructor, where we will create a new method to be called to configure the build system to load our libraries.
inside /Source/UE4Magic/UE4Magic.Build.cs
[Convenience Properties]
public UE4Magic(TargetInfo Target) { [Standard Module Initialization]
LoadBobsMagic(Target);
}
}
LoadBobsMagic accepts a TargetInfo object, which holds a number of configuration elements for the build system, allowing you to customize the build at compilation time. It is passed in to allow us to load in the libs for windows targeting, and can be used later to target other platforms. It also allows you to see if 64 or 32 bit platforms are being targeted, which is gold for our circumstances. If you remember, above I mentioned that we will be targeting x64 machines, but you can use this opportunity to compile out 32bit (x86) libraries as well.
Next we will define a constant to be passed in with the name of the library to link.
inside /Source/UE4Magic/UE4Magic.Build.cs
[Convenience Properties]
[Constructor]
public bool LoadBobsMagic(TargetInfo Target) { bool isLibrarySupported = false;
if ((Target.Platform == UnrealTargetPlatform.Win64) || (Target.Platform == UnrealTargetPlatform.Win32))
{
isLibrarySupported = true;
string PlatformString = (Target.Platform == UnrealTargetPlatform.Win64) ? "x64" : "x86";
string LibrariesPath = Path.Combine(ThirdPartyPath, "BobsMagic", "Libraries");
/\*
test your path with:
using System; // Console.WriteLine("");
Console.WriteLine("... LibrariesPath -> " + LibrariesPath);
\*/
PublicAdditionalLibraries.Add(Path.Combine(LibrariesPath, "BobsMagic." + PlatformString + ".lib"));
}
if (isLibrarySupported)
{
// Include path
PublicIncludePaths.Add( Path.Combine( ThirdPartyPath, "BobsMagic", "Includes" ) );
}
Definitions.Add(string.Format( "WITH\_BOBS\_MAGIC\_BINDING={0}", isLibrarySupported ? 1 : 0 ) );
return isLibrarySupported;
}
}
This is an exceptionally straight forward setup, and not likely to be representative of a fully cross platform build. What we have done is to create the constant WITH_BOBS_MAGIC_BINDING to be passed in at compile time, it is set to 1 (or true).
# Visual Studio 2013/2015 - Linking Our Library
All of the UE4 goodies are taken care of at this point. You can now include your header files and start executing code.
# Startup Module
A little known detail of working with unreal is that you can overwrite the default game implementation and get access to a method executed when your module is started/shutdown, similar to loaded/unloaded. This is not exactly build system related but a common thing that plugin deveopers are likely to be looking for is an initialization point.
inside /Source/UE4Magic/UE4Magic.cpp
- include "Welcome/to/bobsmagic.h"
[Standard Includes]
class FUE4MagicGameModule : public FDefaultGameModuleImpl {
BobsMagic::MagicalBob *PointerToBobsMagic;
/** * Called right after the module DLL has been loaded and the module object has been created */ virtual void StartupModule() override { PointerToBobsMagic = new BobsMagic::MagicalBob();
PointerToBobsMagic->ThankEveryoneForReading();
}
/** * Called before the module is unloaded, right before the module object is destroyed. */ virtual void ShutdownModule() { PointerToBobsMagic->Dispose(); PointerToBobsMagic = NULL; }
};
// Override the default implementation with ours implementation =) IMPLEMENT_PRIMARY_GAME_MODULE(FUE4MagicGameModule, UE4Magic, "UE4Magic");
You can start the Visual Studio Debugger at this point and step through your code, even into the library you compiled, if you linked to a debug build. It will load in the header file from ThirdParty/BobsMagic/Includes/Welcome/to and allow the Libraries to execute as we all expect.
# Marshalling
As you will likely find out quickly, your Library wont be using the same types as in UE4. It is important that you marshall your data between these two in a meaningful and well thought out way. Changing it later may lead to complications.
When binding V8 into UE4 I uncovered a couple of macros in StringConv.h that are used in converting between, Wide Character, Unicode, Strings and C style Character Strings and I recommend you look around for other useful conversions. You may also end up having to create Wrapper objects.
# More Information
I have successfully linked V8 into UE4 and am authoring a module allowing you to use JavaScript as a scripting language to use in your own projects. You can follow development on the forums.
If you are interested in doing something similar I would recommend you look at the V8 Embedders Guide or the source for Node.js.
You can read more about me on my User Page
Retrieved from "https://wiki.unrealengine.com/index.php?title=Linking_Static_Libraries_Using_The_Build_System&oldid=73"