Bonjour a toutes et a tous,

Tout d'abord j'espere etre dans la bonne section du forum pour la question suivante, si cela n'etait pas le cas je fermerais le topic et je m'en excuse d'avance .

Voilà, j'ai un programme en construction qui est un moteur de jeu 2D.Bref, il y a la possibilitée d'implementer des fonctions afin de gérer ses IAs et ses personnages principaux.Donc il me faut un compilateur qui puisse cree des DLL qui seront exploiter lors de la compilation du jeu construit par l'utilisateur.Ma question sera simple :

Celon les droit GPL de GNU et de son compilateur MinGW est ce que je peux le fournir avec mon executable. En admettant que mon programme soit payant ?

Voilà j'espere m'etre fait bien comprendre et je vous remercie de votre attention ...

MinGW a écrit:

MinGW Runtime: All releases of the MinGW base runtime package, prior to release 4.0, have been placed in the public domain, and are not governed by copyright. This basically means that you can do what you like with the code.
Due to inadmissibility of the public domain concept, in certain jurisdictions, we have now chosen to adopt a MIT style license for the principal components of the MinGW runtime, from release 4.0 onwards; you may view this LICENSE, as it is filed in the source code repository.

....

w32api: In the case of releases prior to 4.0: you are free to use, modify and copy this package. No restrictions are imposed on programs or object files linked with this library. You may not restrict the the usage of this library. You may distribute this library as part of another package or as a modified package if, and only if, you do not restrict the usage of the portions consisting of this (optionally modified) library. If distributed as a modified package, then a copy of this notice must be included.

...

WSL: We have combined the MinGW runtime package and the w32api package into one, which we have dubbed WSL, (an acronym for Windows System Libraries). We have applied a MIT style license to the sources, (where this does not conflict with any existing licenses applying to specific sub-components). You may view this LICENSE, as it is filed in the source code repository

...

MinGW Profiling Code: MinGW profiling code is distributed under the terms of the GNU General Public License, Version 2.

Binutils, GCC, GDB, GNU Make: All of the GNU development tools, such as GNU binutils, GCC, GDB and GNU Make, are governed by the terms of the GNU General Public License; (note that this may be GPLv2 or GPLv3, depending on the preferences of the upstream maintainers, and the specific version of each package which you choose to install; in most cases, the most recent versions are likely to be GPLv3, while older versions may be GPLv2).

MinGW a écrit:

Binaries created from the use of MSYS and of MinGW are not bound by any license found within this package unless you use a library that is itself covered by the GPL license. If you wish to create proprietary software then don't use libiberty.a or any other GPL licensed library. A library licensed with LGPL (Lesser GPL) may be used by proprietary software without GPL infection as special permission within the LGPL has given you this right.

So essentially unless you end up explicitly linking against msys-1.0.dll, programs built in MSYS shell using MSYS tools are not infected with GPL. Compiling and linking inside MSYS shell or using MSYS tools alone does not automatically link against the dll.

En gros c'est possible avec la version > 4.0. Par contre faut faire attention à certains modules qui peuvent être GPL et qui pourrait infecter toute la chaîne, surtout si tu souhaite que les utilisateurs puissent vendre sans distribuer leur code des créations par ton moteur.

Par contre je doute que tu puisse "embed" le compilateur directement, dans ce cas je regarderais du coté de Clang qui est prévu pour ça

Clang a écrit:

We actively intend for clang (and LLVM as a whole) to be used for commercial projects, not only as a stand-alone compiler but also as a library embedded inside a proprietary application. The BSD license is the simplest way to allow this. We feel that the license encourages contributors to pick up the source and work with it, and believe that those individuals and organizations will contribute back their work if they do not want to have to maintain a fork forever (which is time consuming and expensive when merges are involved). Further, nobody makes money on compilers these days, but many people need them to get bigger goals accomplished: it makes sense for everyone to work together.

Un grand merci pour ces infos parfaitement clair je prend note et me dirige vers Clang