Packaging Project: Error missing precompiled manifest for plugin

Development Pipeline & Plugins Plugins
, , ,
1

I am experiencing an issue packaging a project that uses a code plugin I also created.

The steps I have taken are as follows:

  • Created a project
  • Created a project plugin within that project, and developed the plugin
  • Set plugin platform whitelist to Win32 and Win64
  • Confirmed plugin compiles correctly by compiling all platforms in VS, and packaging the plugin in the editor
  • Copied the plugin into Engine/Plugins/Runtime
  • Edited the uplugin file, set engine version and Installed to true
  • Created another project (examples project), enabled the custom plugin
  • Created content in the examples project that uses objects from the code plugin
  • Tested content as working correctly in PIE
  • Successfully cooked examples project in windows

However, when I attempted to package the examples project itself, I receive the following error:

ERROR: Missing precompiled manifest for ā€˜TestPluginā€™. This module was most likely not flagged for being included in a precompiled build - set ā€˜PrecompileForTargets = PrecompileTargetsType.Any;ā€™ in TestPlugin.build.cs to override

I am unable to resolve this problem.

I tried adding ā€˜PrecompileForTargets = PrecompileTargetsType.Anyā€™ into the plugin build cs file, but it didnā€™t make any difference. The uproject file for the example does list the plugin in the Plugins section, which is set to enabled. The uplugin file defines the plugin module, sets the type to runtime, sets loading phase to default, and has the whitelisted platforms.

I am unable to find any other threads regarding ā€œprecompiled manifestā€ other than this one (Packaging is not successful - Platform & Builds - Epic Developer Community Forums), but that doesnā€™t resolve my problem, because the plugin is already included in the example project.

Has anyone else experienced this issue and know how to resolve it?

2

Wish I could help, but I want to say that I have experienced the same thing as well.

I will let you know if I figure anything out today.

3

Hi! And i have this problemā€¦

4

I had the same issue when I tried to package for Linux.
I fixed it by copying the plugin in the project folder (it may need to be in both folders).

I hope itā€™ll help you.

7 Likes
5

Yep, that worked for me! We shouldnā€™t have to do that anyway, really stupid.

6

Iā€™m having the
problem. The only ā€œsolutionā€ I found is by manualy changing Enabled to false in my .uproject file.
I need to find out more about this issue.

{
ā€œFileVersionā€: 3,
ā€œEngineAssociationā€: ā€œ4.22ā€,
ā€œCategoryā€: ā€œā€,
ā€œDescriptionā€: ā€œā€,
ā€œPluginsā€: [
{
ā€œNameā€: ā€œHoudiniEngineā€,
ā€œEnabledā€: false
}
]
}

7

The strategy about plugin developing is always changing from UE4.14 to UE4.24, Iā€™ve had enough.

After UE4.20(inclusive), if you want to release your plugin as binary built style, and let users can use your plugins by putting them under project folder, you can try this:

  1. Package your plugin. Open Edit->Plugins, in the plugins list, locate your plugin, click the [package] text, and pick a destination folder, then your plugin will be packaged very well. Notice: this compiling method is more strict than visual studio does, so you may need to modify your c++ code a little bit, especially the #include statements.
  2. After you have packaged your plugin, add bUsePrecompiled = true; to your plugin build.cs file. Save it.
  3. Zip the packaged plugin, send to user.

For me, the above instructions works well for usersā€™ BP projects. But for usersā€™ C++ projects, exactly for Debug configuration C++ project, it not work! Because, the package operation above is only package the Develop/DevelopEditor configuration for your plugin. I was in great pain about this ā– ā– ā– ā– . Finally, I choose to modify the UBT C# code to let the package operation also build the Debug/DebugEditor configuration for plugin. If some one need, then I paste the modifications at here.

1 Like
8

u will lose the plugin content or programmer support when you disable the plugin it is not the solution for engine plugin dev.

9

your answer is the totally correct answer !!!
Thanks a lot dude!
å¤šč°¢äŗ† 哄们å„æ~ åø…å“„ ē•™äøŖå¾®äæ”吗ļ¼Ÿå“ˆå“ˆå“ˆ

10

what about Missing precompiled manifest for ā€˜AdvancedSessionsā€™?
Ive tried what I understand here but with no results? Not using C++

1 Like
11

can you show how to make this modification. I downloaded someones plugin and Im having this issue. I have no clue how to use C# or where to add this line. Thanks : )

12

After UE4.24(inclusive), I recommend that users put plugins under (EngineInstalledPath )/Engine/Plugins folder.

13

Where is this plugin build.cs because I canā€™t find it anywhereā€¦

14

go to the folder of your plugin, then to the folder that says ā€œSourceā€ and go to where it says the name of your plugin and you will find the .Build.cs file

15

Hey if youā€™re still struggling follow this short video. Take the precompile folders and add it directly to the server folder for your specific Project (309) Missing Precompiled manifest ā€™ ā€™ his module was most likely not flagged for being ----- - YouTube

16

cheers that worked, was the exact issue with Linux here