Re: MinGW Ada compiler licence question targeting commercial applications

["Hibou57 (Yannick Duchêne)" <yannick_duchene@yahoo.fr>]

On 18 juin, 21:50, Hibou57 (Yannick Duchêne)
<yannick_duch...@yahoo.fr> wrote:
> The second link gives the definition of “Independent Module” as was
> looking for :

It also contains the definition for “Eligible Compilation Process” :

(the second part is the most important, but the second is required to
understand the second one)

> When you compile those source code files, they usually go through a series of
> steps:source code generation, preprocessing, compilation to low-level code,
> assembling, and linking. Not all projects follow all these steps, depending on
> what language you're using and how it's written, but they'll always go in this
> order, and everyone using GCC will go through the process of compiling
> high-level code into some low-level language such as assembly code or Java
> bytecode. This phase is when GCC combines or links your own code with code
> from the GCC libraries. We call it the “Compilation Process.” The output you
> get from it is called “Target Code,” as long as that output is not used as
> compiler intermediate representation, or to create such an intermediate
> representation.
>
> In order to take advantage of this permission, the Compilation Process that
> you use to create Target Code has to be “Eligible,” which means that it does
> not involve both GCC and GPL-incompatible software. It's important to remember
> that the Compilation Process starts when you feed any high-level code to GCC,
> and ends as soon as it generates anything that can be considered Target Code.
> [...]