[fpc-devel] RTTI interface & variant late binding issue (mORMot)

Florian Klämpfl florian at freepascal.org
Sat Feb 7 13:15:38 CET 2015

Am 07.02.2015 um 13:07 schrieb Jonas Maebe:
> On 07/02/15 12:34, Florian Klämpfl wrote:
>> Am 07.02.2015 um 12:14 schrieb Jonas Maebe:
>>> To me, the optimal solution would be to simply use libffi (you would
>>> only need logic to translate the rtti for the parameter types to libffi
>>> format, and it would automagically work for all platforms), but since
>>> that's an external dependency I guess that's not acceptable.
>> Well, the technical aspect is one thing, but its license is another issue. Violating it happens too
>> quick.
> The libffi license is basically a BSD license, 

This is already the issue :)

> that's no problem at all:

There is imo a big one: just compiling a small program containing libffi and give it to another
person without a libffi copyright notice is a license violation.

Using libffi in core parts of the rtl would mean even the smallest fpc program would need to come
with a libffi copyright notice either by a readme or some command line option to display copyrights.

> https://github.com/atgreen/libffi/blob/master/LICENSE

More information about the fpc-devel mailing list