How to handle FMOD in an open source project?

[wobbier]

I have an open source engine for fun/learning purposes. I’m starting to wonder about the ability to distribute builds via Github Actions.

For further reading purposes, FMOD in my engine is currently behind a define and can only work if you clone the repo locally and build with FMOD installed.

What are my options here?
Am I allowed to build and link against fmod via github?
Is there any workarounds besides going private and distributing a zip?
Does purchasing a license even make a difference even though I’ll have like 1 download?

My project is essentially useless without FMOD and then github actions just becomes a build success/fail tool.

I’m curious of your thoughts.

[wobbier]

FMOD Github procedure

The official stance is that users should only download from FMOD the FMOD site currently. We allow binaries to be distributed (ie for a non engine, fmod.dll would be ok to distribute), but not the full api. The more this happens the more unofficial sources of the API there are and then people are sourcing old versions from non official sites more often than coming to fmod.com to get updated builds, documentation, examples and support. We have the ability to do engine licenses for people that …

Looking at this, is there a middle ground for this or am I basically fucked?

My project is non-commercial btw

[Andrew]

Our stance hasn’t changed, you’re still not allowed to host your own copy of the FMOD APIs or tools on github or anywhere else unless you have a specific license allowing you to do so. Maybe there’s a non-commercial alternative that would suit your project?

[wobbier]

let’s say I install it on a build machine, so then the api files/lib/dll is never committed into the git repo?

but the zip produced would include the dll

[Andrew]

If you’re not hosting the FMOD API or tools somewhere publicly available then that would be ok.