Distributing plugin without source
Contrary to the numerous references in plugin documentation .build.cs files are now required for distributing plugins without source. This is also referenced in the forum but has not been fixed in the documentation.
Can the documentation be fixed?
Additionally, there is no mention of the proper way to distribute the libs to the user. The libs are created with a ProjectName-PluginModuleName.lib naming convention. But the user's ProjectName will differ from my ProjectName.
Am I supposed to tell the user to rename the libs that I provide for each of their projects?
asked Aug 05 '15 at 10:04 PM in Bug Reports
The documentation is currently correct, the problem is that this build.cs problem is actually a bug. We are currently working on fixing that at the moment. As for your second question, the library names have project-agnostic names if you return true from ShouldUseSharedBuildEnvironment() in your .target.cs file (that function defaults to returning true in binary releases, which is how we allow distributing precompiled plugin binaries). Thank you for letting us know that this isn't mentioned in the documentation, I'll look into adding this information to the documentation personally.
As for distributing your plugin without the source, we would recommend that you include the source so that people who are using a source version of the engine can build the plugin with their version of the engine, otherwise only binary users will be able to use it.
Have a nice day,
answered Aug 10 '15 at 07:55 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here