# Dynamic C license clarification?

**URL:** <https://forums.digi.com/t/dynamic-c-license-clarification/36375>\
**Category:** Rabbit Software\
**Created:** [April 15, 2025, 8:04am UTC](https://forums.digi.com/t/dynamic-c-license-clarification/36375 "2025-04-15T08:04:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![spth](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@spth](https://forums.digi.com/u/spth)\
**Post date:** [April 15, 2025, 8:04am UTC](https://forums.digi.com/t/dynamic-c-license-clarification/36375/1 "2025-04-15T08:04:25Z")

</div>

When installing Dynamic C 9 or 10, one gets presented with a license dialog, that one has to accept. It starts with

This MPL 2.0 license covers the majority of this project with the  
following exceptions: [list of exceptions for some sample code and libraries]

I am not a lawyer, but to me this looks like Dynamic C itself is now under MPL 2.0, and what I am allowed to do with Dynamic C is what the MPL 2.0 allows. MPL 2.0 is a free software license, it allows redistribution. One of its conditions is that if I give the software on to someone else, I have to also give the source code. While source code for samples and libraries is on GitHub, I do not have access to the source code of the Dynamic C compiler. So how should I comply with the terms of the license when giving Dynamic C to someone else?  
I guess since the binary is all I have, to me, this binary would be the “the form of the work preferred for making modifications”, i.e. “source code form”, as defined by MPL 2.0 since I have no other form better suited for modification? A bit unfortunate, but that should work.  
So according to my understanding I could e.g. put the Dynamic C 9.62A and 10.72E installers on GitHub, so people can still download them from there in case Digi stops providing the download.

---

<div class="post-metadata">

**Author:** ![TomCollins](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/tomcollins/32/37_2.png) [@TomCollins](https://forums.digi.com/u/TomCollins)\
**Post date:** [April 15, 2025, 5:13pm UTC](https://forums.digi.com/t/dynamic-c-license-clarification/36375/2 "2025-04-15T17:13:18Z")

</div>

The intent was for the MPL 2.0 license to apply to source code provided with Dynamic C – specifically the source code in the Github repositories.

Binaries from the installer, and the installer itself are not covered by that license.