LEGACY DOCS · 12.0Stable is 13.2. This page stays because it still owns historical or unchanged contracts.CURRENT 13.2 →
RELEASE LINE13.2 HISTORICAL13.1 PREDECESSOR13.0 PREVIOUS12.4 NATIVE MIRARCHIVE

V12.0 BASE CONTRACT

License FAQ

Practical GPL-2.0-only questions, runtime-exception boundary and the distinction between compiler use and covered code.

This is a documentation FAQ, not legal advice. The authoritative license text shipped with the v12.0.0 source is GPL-2.0-only.

does using the compiler force my source to be GPL?§

Merely processing your source with a GPL compiler does not by itself make your source code a derivative of the compiler. The supplied DByte materials, however, do not document a special runtime-linking exception.

Distribution obligations can depend on what GPL-covered code is copied into or linked with the distributed work. The supplied contract does not define a runtime exception, so do not assume one exists.

what is definitely covered?§

DByte itself and modified/redistributed covered source remain governed by the GPL-2.0-only text shipped with the release. For distribution decisions with legal consequences, read that license and obtain appropriate legal advice.

where is the license authority?§

The release/source license file is the authority. Website summaries are secondary and must not silently weaken or broaden it.

SOURCE POLICY: release/tag documents define contracts; examples are copied from the supplied v12.0.0 package or explicitly marked as explanatory. Unsupported claims are not upgraded by prose.