On Sun, Mar 24, 2019 at 6:22 PM Bart <bartjun...@gmail.com> wrote: > Extract from fpc.cfg from 3.0.4 (created by offcial installer) > # searchpath for units and other system dependent things > -FuC:\devel\fpc\3.0.4/units/$fpctarget > -FuC:\devel\fpc\3.0.4/units/$fpctarget/* > -FuC:\devel\fpc\3.0.4/units/$fpctarget/rtl > > Extract from fpc.cfg from fpc trunk: created with fpcmkcfg.exe (from trunk) > # searchpath for units and other system dependent things > -Fu/units/$fpctarget > -Fu/units/$fpctarget/* > -Fu/units/$fpctarget/rtl >
The fpc.cfg created by the installer is correct. The one created by default by fpcmkcfg is not (for Windows), as the relative-but-not-really paths like that have no meaning on Windows. To be properly cross-platform, it should really generate something like "-Fu..\..\units\$fpctarget" and such, if the assumption is that it's being invoked from the "bin\$fpctarget" directory.
_______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
