Making package for Linux

Hi

I’m trying to cook a package for Linux and get the following error:

ERROR: Exception in AutomationTool: No files found to deploy for D:\UE4\UnrealEngine\Engine\Binaries\Linux with wildcard UE4Game and exclusions

The project is just the “blank” project with the two chairs and the table. I’ve add the extra dependencies for Linux and I’ve compiled the editor with the development configuration. I can make the win64 packages with no problems.

It looks like the script is having problem finding a lot of assets, so I’ve tried to remove all the assets from the scene and from the content browser(deleted the files). But the script is still looking for them. This also makes the Win64 packages fail, which is properly another problem.

I’ve attached the log. Does anyone know what might cause this problem ?

link text

Seems like you are packaging a content-only project, so you need to manually build UE4Game first. We don’t ship UE4Game Linux binary by default (perhaps we should), and packaging content-only projects doesn’t rebuild binaries by themselves.

You can do that with by building UE4 target in Development (or Shipping, depending on your intended use) configuration for Linux platform, with cross-toolchain supplied (A new, community-hosted Unreal Engine Wiki - Announcements - Epic Developer Community Forums).

Hope this helps.

Great. I guess I missed the part about compiling the UE4 for Linux. Now I can build the “blank” project for Linux without problems.

I still get errors when I try to make a package(Win64) for another project, where I’ve removed some of the standard assets. I’ve attach the log

Hello,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes. If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar error, that is not 100% related, could you please submit a new report for it.

Thanks!