Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On 3/25/19 6:24 PM, Bart wrote: On Mon, Mar 25, 2019 at 1:55 PM Joost van der Sluis wrote: 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'. As an end user howvere I do

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

Ben Grasset schrieb am Di., 26. März 2019, 13:47: > On Tue, Mar 26, 2019 at 2:33 AM Sven Barth via fpc-devel < > fpc-devel@lists.freepascal.org> wrote: > >> Those paths are not handled relative to the compiler binary, they are >> handled relative to the current directory when calling the

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Tue, Mar 26, 2019 at 2:33 AM Sven Barth via fpc-devel < fpc-devel@lists.freepascal.org> wrote: > Those paths are not handled relative to the compiler binary, they are > handled relative to the current directory when calling the compiler. The > compiler does not differentiate whether a

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

Am 26.03.2019 um 01:08 schrieb Ben Grasset: On Mon, Mar 25, 2019 at 5:34 PM Ben Grasset > wrote: To be properly cross-platform, it should really generate something like "-Fu..\..\units\$fpctarget" I meant to say, "generate something like that specifically

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Mon, Mar 25, 2019 at 5:34 PM Ben Grasset wrote: > To be properly cross-platform, it should really generate something like > "-Fu..\..\units\$fpctarget" > I meant to say, "generate something like that specifically for Windows." Perhaps just have an IFDEF UNIX ELSE ENDIF block to

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Sun, Mar 24, 2019 at 6:22 PM Bart 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

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Mon, Mar 25, 2019 at 1:55 PM Joost van der Sluis wrote: > 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'. As an end user howvere I do not even know that such a thing

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

Am 25.03.2019 um 14:43 schrieb Joost van der Sluis: > When you discover things like this, it's better to report it. That way > you avoid double work for others with the same problem. That piece was from way back when the footnote statement of "Don’t write about Laz/FPC-Bugs, I’m not involved in

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

Op 25-03-19 om 14:07 schreef Martok: I used '-o "%CD%\fpc.cfg"' exactly because fpcmkcfg does not handle relative paths well. When you discover things like this, it's better to report it. That way you avoid double work for others with the same problem. Regards, Joost. --

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

Hi, this is what I supply with the snapshot builds: https://pastebin.com/KseAwBAM The multicall binary lives in $(LazarusDir)\fpc\$FPCVer\bin\$TargetCPU-$TargetOS\fpc.exe This script is in $(LazarusDir)\makeconfig.cmd You'll notice this is the default Windows Installer path structure and

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

Op 25-03-19 om 11:48 schreef Bart: On Mon, Mar 25, 2019 at 10:45 AM Joost van der Sluis 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

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Mon, Mar 25, 2019 at 11:48 AM Bart wrote: > fpcmkcfg -d does not show the existence of a build-in BASPEPATH though. Yeah, -m of course (as the line below that correctly showed)... ___ fpc-devel maillist - fpc-devel@lists.freepascal.org

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Mon, Mar 25, 2019 at 10:45 AM Joost van der Sluis 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.

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Mon, Mar 25, 2019 at 11:25 AM Sven Barth via fpc-devel wrote: > I replied to wkitty42's statement regarding relative paths, not your problem > per se. I know, but the discussion gets side-tracked this way. The main questions are: 1. Why can fpc find all rtl files if -Fu parameters are like

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

Bart schrieb am Mo., 25. März 2019, 10:46: > On Mon, Mar 25, 2019 at 7:50 AM Sven Barth via fpc-devel > wrote: > > > Well, to be fair, the "\bla" ones are called "drive relative paths" as > they're always relative to the root drive of the current directory. > > Well if fpc treats -Fu/bla as

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Mon, Mar 25, 2019 at 10:45 AM Joost van der Sluis wrote: > ERhm... I can not think of any design that makes this logical. I'm not > the one who builds and maintains the windows installers, though. So it's > a bug, I would say. Reported as https://bugs.freepascal.org/view.php?id=35271 --

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Mon, Mar 25, 2019 at 10:45 AM Bart wrote: > Why the difference between the 2 fpc.cfg's (3.0.4 vs trunk; I assume > both used fpcmkcfg tool)? Joost answered that while I was typing -- Bart ___ fpc-devel maillist -

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On Mon, Mar 25, 2019 at 7:50 AM Sven Barth via fpc-devel wrote: > Well, to be fair, the "\bla" ones are called "drive relative paths" as > they're always relative to the root drive of the current directory. Well if fpc treats -Fu/bla as drive relative paths, it makes even less sense that: 1.

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

Op 24-03-19 om 23:21 schreef Bart: 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

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

schrieb am Mo., 25. März 2019, 03:31: > On 3/24/19 6:21 PM, Bart 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/* > >

Re: [fpc-devel] fpcmkcfg and fpc.cfg questions

On 3/24/19 6:21 PM, Bart 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

[fpc-devel] fpcmkcfg and fpc.cfg questions

Hi, First problem: I tried to build lazarus trunk with fpc trunk. Lazarus r60747, fresh checkout Fpc r41788, installed from source in C:\PP It failed with: C:\devel\laztrunktrunk\packager\registration\fcllaz.pas(11,3) Fatal: (10022) Can't find unit db used by fcllaz I took a look at my fpc.cfg