Question 1

How to set up makelove for automated builds on GitHub Actions?

Accepted Answer

Use the example YAML file from the README, adapting it for your project's directory and build settings. Ensure you configure secrets for uploads and note that it's best for unversioned builds unless you automate version input from a file.

Question 2

Can makelove package games with custom DLLs or shared libraries?

Accepted Answer

Yes, makelove handles shared libraries for Lua modules and FFI by including them in builds. However, for web targets via love.js, these libraries are not supported due to love.js limitations.

Question 3

What's the difference between makelove and love-release?

Accepted Answer

makelove offers more extensive multi-platform support, versioned builds, and hooks for automation, while love-release is simpler and lighter. Choose makelove for complex, CI/CD-driven workflows requiring customization.

Question 4

How to add a custom icon to Windows executables in makelove?

Accepted Answer

Specify the icon path in the makelove.toml configuration under Windows targets, but this requires a Windows environment or Wine to apply the metadata, as noted in the README.

Question 5

Does makelove support building for mobile platforms like Android?

Accepted Answer

No, makelove is focused on desktop (Windows, Linux, macOS) and web platforms. For mobile, you need to use other löve2D tools or export methods specific to those ecosystems.

Question 6

How to use pre-build hooks to dynamically include assets in makelove?

Accepted Answer

Define a pre-build hook in your TOML that executes a script, using environment variables like MAKELOVE_TEMP_CONFIG to modify the configuration file on the fly, such as parsing asset lists for inclusion.

makelove

What is makelove?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions