Re: How to use gprbuild with FSF GNAT Windows compilers 64 and 32 bit

[David Botton <david@botton.com>]

> Licensing question:  Is it that this specific implementation of gpr-tools doesn't make executables fall under the standard GPL license when used or is that true for all implementations (including the one from GNAT GPL from AdaCore that is used with the GPS IDE)?  I.E. can I use GPS, have it link to the AdaCore tools for gprbuild, but also link to the FSF GNAT instead of the AdaCore GNAT and be able to make products with the FSF style license?  Or does the fact that the tools come from AdaCore make them have a different affect on the license?

The way AdaCore encumbers your code is by removing the runtime linking exceptions (this is legal and a "feature" of the GPL runtime exception). As long as you are not using the AdaCore "GPL" runtimes you are code can be under any licenses you choose as per the GPLv3 run time exception.

> Realistically, I would still used the tools you are linking with the FSF version of GNAT, but was curious so I know what my options are.

You could can use FSF GNAT with GPS (I often do) or any other GPL tools and still no licensing issues. You could even use the GPL version until release time and then just recompile with FSF GNAT if you do not with to have a GPL product. However if your final product is under the GPL (I encourage that!) there is no reason in particular to choose FSF GNAT over AdaCore's shareware product. Of course if you fit their target market I highly encourage buying their support product, it helps support GNAT and Ada development, and is in fact the best support I've seen of any compiler anywhere.

The efforts I make to encourage use and development with FSF GNAT has to do with the fact that GPL virused run times damages the greater Ada community by discouraging those not in AdaCore's target market, Open Source developers not wishing to use the GPL, small businesses and startups.

David Botton