[fpc-devel] (Re)compiling FPC or is there something like fpc.bpg?

Adem listmember at letterboxes.org
Sat Jul 24 13:40:00 CEST 2010

  On 2010-07-24 1:28 PM, Graeme Geldenhuys wrote:
> This is easy to do with a few IFDEF lines...
>> {...}
> {$ENDIF}
>>   {...}
> {$ENDIF}
> Now if APROGRAM is defined, they act as self-contained programs. If
> not, they act as include files and can be combined.
There are 115 'fpmake.pp' files in the trunk --(or more, because I 
haven't yet been able to get a full local copy of the FPC).

Even then, I have no guarantees that those files are up-to-date.

While I am prepared to do the manual work, I don't know enough about 
FPC's internals to decide what should be in those files.

Meaning, I would need a lot of hand holding along the way.

Boy, I could kill for a 'makefile' parser...
>> in a file called, say, 'fpmake.pp.inc'.
> FPC doesn't care about the file extension, so you can name them all
> *.pas (even if they are include files - no APROGRAM define exists).
Actually, ATM, I am inclined towards generating an XML file which holds 
all the necessary info.

Any comments on that?

More information about the fpc-devel mailing list