[fpc-pascal] releasing commercial components as PPU files

michael.vancanneyt at wisa.be michael.vancanneyt at wisa.be
Mon Oct 22 15:36:16 CEST 2012

On Mon, 22 Oct 2012, Graeme Geldenhuys wrote:

> On 2012-10-22 14:15, michael.vancanneyt at wisa.be wrote:
>> That will most probably not work, although maybe -Ur may provide a solution.
> Isn't -Ur a default compiler option in official releases? So a 'make
> all' in the FPC 2.6.0 source directory should use the same compiler
> options on every Linux setup etc, and be identical to say the binary FPC
> 2.6.0 Linux release file. Obviously taking into account the same bit
> size (32-bit or 64-bit Linux).
> Saying that, looking at the released files on SourceForge again - all
> releases on Linux, FreeBSD etc have binary releases, so maybe the
> problem is not so much of an issue, because the officially released FPC
> versions will be consistent across Linux or FreeBSD. And that's the
> version I'll support in my components. This is just like Delphi then.
>> It is a discussion I have had several times, and usually the result was
>> negative. As soon as any of the dependencies is recompiled, there are
>> problems.
> That's why I'm saying only official FPC releases will be supported in
> the PPU versions of my components. If they want to use FPC 2.6.x (fixes
> branch) or FPC 2.7.1, then they must buy the source code version of my
> components.

Like I said, it may work. 
But I think you are in trouble as soon as someone uses e.g. lazarus.

I am not sure whether they use the binary release of fpc, or if they compile
their own for e.g. windows. If it is the latter, you're in problems.

IMHO, in the end it is not worth the trouble.


More information about the fpc-pascal mailing list