# Can we commit the FMOD API to our integration libraries on github?

**URL:** <https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751>\
**Category:** FMOD Engine\
**Created:** [May 10, 2020, 4:14pm UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751 "2020-05-10T16:14:24Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shadoninja](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@Shadoninja](https://qa.fmod.com/u/Shadoninja)\
**Post date:** [May 10, 2020, 4:14pm UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/1 "2020-05-10T16:14:24Z")

</div>

I am currently working on an FMOD integration for Haxe. Are we allowed to commit the FMOD API files to our repo or include them in our releases?

---

<div class="post-metadata">

**Author:** ![brett](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/brett/32/261_2.png) [@brett](https://qa.fmod.com/u/brett)\
**Post date:** [May 10, 2020, 11:49pm UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/2 "2020-05-10T23:49:32Z")

</div>

Hi ,  
You are allowed to redistribute the dlls only typically with a product.  
If there are more files involved for compilation, we typically dont want the SDK broken up into parts. This is why we recommend users download the full package from our website.

---

<div class="post-metadata">

**Author:** ![Shadoninja](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@Shadoninja](https://qa.fmod.com/u/Shadoninja)\
**Post date:** [May 11, 2020, 2:16am UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/3 "2020-05-11T02:16:53Z")

</div>

I am sorry, but I don’t understand if my library is considered a product or not: [github repo](https://tanneris.me/haxe-fmod)

---

<div class="post-metadata">

**Author:** ![brett](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/brett/32/261_2.png) [@brett](https://qa.fmod.com/u/brett)\
**Post date:** [May 11, 2020, 3:28am UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/4 "2020-05-11T03:28:48Z")

</div>

When I say product I mean a released game or application.  
If if are writing a wrapper for sometihng, the dll rule still applies. I can’t see any fmod API files in that github repro (maybe im not looking hard enough), but generally it is ‘dll only’

---

<div class="post-metadata">

**Author:** ![Shadoninja](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@Shadoninja](https://qa.fmod.com/u/Shadoninja)\
**Post date:** [May 11, 2020, 3:58am UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/5 "2020-05-11T03:58:56Z")

</div>

I am explicitly leaving the API out of the repo as to not break the rules. The readme explains how the user can download it and put it into the library once they clone it down or pull it in using a package manager. The only files the repo relies on are fmod.dll, fmodstudio.dll, and fmodstudio\_vc.lib (provided by the user)

---

<div class="post-metadata">

**Author:** ![brett](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/brett/32/261_2.png) [@brett](https://qa.fmod.com/u/brett)\
**Post date:** [May 13, 2020, 3:16am UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/6 "2020-05-13T03:16:05Z")

</div>

im ok to include the libs as they are pretty much bound to each other , just make sure the user is aware fmod is not a free library if they use it.  
Brett

---

<div class="post-metadata">

**Author:** ![Shadoninja](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@Shadoninja](https://qa.fmod.com/u/Shadoninja)\
**Post date:** [May 13, 2020, 3:39am UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/7 "2020-05-13T03:39:57Z")

</div>

Thank you! I have added a note to the first section of the readme regarding your license.

---

<div class="post-metadata">

**Author:** ![SparkerInVR](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@SparkerInVR](https://qa.fmod.com/u/SparkerInVR)\
**Post date:** [November 12, 2022, 4:27pm UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/8 "2022-11-12T16:27:22Z")

</div>

I am the Head of Development of [FlyWithLua](https://github.com/sparker256/FlyWithLua) which is a plugin for X-Plane. I have added Fmod support but have not added the FMOD API to the repo because I wanted to make sure that would be OK if I followed the same rules posted above.

---

<div class="post-metadata">

**Author:** ![brett](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/brett/32/261_2.png) [@brett](https://qa.fmod.com/u/brett)\
**Post date:** [November 13, 2022, 10:26pm UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/9 "2022-11-13T22:26:33Z")

</div>

yes import libraries, static libraries and dynamic libraries are ok to distribute / store in a repo.  
edit: and headers so that it will compile.  
regards,  
Brett

---

<div class="post-metadata">

**Author:** ![SparkerInVR](https://avatars.discourse-cdn.com/v4/letter/s/bbce88/32.png) [@SparkerInVR](https://qa.fmod.com/u/SparkerInVR)\
**Post date:** [November 13, 2022, 11:44pm UTC](https://qa.fmod.com/t/can-we-commit-the-fmod-api-to-our-integration-libraries-on-github/15751/10 "2022-11-13T23:44:06Z")

</div>

Thanks for the info and have tried to make it clear that Fmod is not a free Library.
