[fpc-devel] fpcmkcfg and fpc.cfg questions

Joost van der Sluis joost at cnoc.nl
Mon Mar 25 13:55:37 CET 2019

Op 25-03-19 om 11:48 schreef Bart:
> On Mon, Mar 25, 2019 at 10:45 AM Joost van der Sluis <joost at cnoc.nl> wrote:
>> To create a working fpc.cfg, you have to provide the %basepath% on the
>> command-line. (There are a few build-in macro's, you can see them using
>> 'fpcmkcfg -m')
> fpcmkcfg -d does not show the existence of a build-in BASPEPATH though.

That's correct. That's why it should be provided on the command-line.

fpcmkcfg only shows the values of all defined macro's. For example, try 
'fpcmkcfg -d foo=jojo -m'.

The built-in macro's are there because they need some sort of logic. 
Like the BUILDDATE and BUILDTIME which will contain the current 
date/time. FPCTARGET the processor fpcmkcfg is compiled for etc.

> C:\pp\bin\i386-win32>fpcmkcfg -m
> BUILDDATE=25-3-2019
> BUILDTIME=11:45:25
> COMPILERCONFIGDIR={LocalRepository}config/
> FPCBIN=fpc
> LOCALBASEPATH=$LOCAL_APPDATA\FreePascal\fppkg   //odd name for fppkg
> specific folder?

It's being used for ages... You mean the 'FreePascal' part?



http://lazarussupport.com - Your donation helps to push Free Pascal and 
Lazarus forwards.

More information about the fpc-devel mailing list