On Tue, 25 May 2010 11:06:53 +0200 Graeme Geldenhuys <[email protected]> wrote:
> On 25 May 2010 10:13, Vincent Snijders wrote: > > > > And if you copy the options in Show options to a command line after the > > compiler path, what happens then? > > OK, I finally figured out the problem. My *.cfg files had one line in > them listing all the compiler parameters one after the other. > > Lazarus or FPC never listed any problems with that, as the compiler > output below shows. It also (silently) never used any of the options > in the *.cfg file. But as soon as I change my *.cfg files to list one > parameter per line, then it compiles correctly. > > So the problem actually sits with FPC. To highlight this problem, I > simply need to modify my *.cfg files to have multiple lines, but make > of the the lines contain more than one compiler parameter. Instantly > FPC fails to compile the project, but having them all on one line it > doesn't. AFAIK this was always the case. I also stumbled in this trap some years ago. It would be nice if the standard fpc.cfg would mention this in the start comments. Lazarus does not parse the configs directly. It lets fpc parse it and watches the -va output. >[...] > > Thanks for helping me narrow down the issue. I'll report this bug in > Mantis, FPC project. Mattias -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
