Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2012-09

building lazarus 1.0 with make OPT="-n" and fpc.cfg in different location

7 messages · 6 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Seth Grover

Greetings. First off, congratulations on the 1.0 release. Lazarus is a terrific IDE and a great development platform.

I've got a script that I use to build FPC/Lazarus from source and roll it into my own custom package. During the build of Lazarus, /etc/fpc.cfg doesn't exist yet. This isn't a problem for the most part, because I used samplecfg to generate an fpc.cfg file in a temporary location. Then, when building Lazarus, I do it like this:

make bigide PP=/path/to/wherever/ppcx64 OPT="-n @/path/to/tmp/fpc.cfg"

The -n tells it to not use the regular cfg paths, and what follows tells it where to find the cfg file to use.

This works fine for most of the build: lazarus builds and links, as does startlazarus and some of the other binaries. However, when it gets to building the "lhelp" binary under chmhelp, I can see my OPTs aren't being passed down, and it fails with an error that /etc/fpc.cfg doesn't exist.

I've worked around it by symlinking /etc/fpc.cfg to my temporary file, but it would be better if it worked correctly.

Thanks,

-SG

This email is fiction. Any resemblance to actual events or persons living or dead is purely coincidental. Seth Grover

Reply by email

waldo kitty
to Seth Grover
Seth Grover wrote 5 lines
make bigide PP=/path/to/wherever/ppcx64 OPT="-n @/path/to/tmp/fpc.cfg" The -n tells it to not use the regular cfg paths, and what follows tells it where to find the cfg file to use.

i don't know if this ties in or not but your make line appears to be missing a space between the closing double-quote and the '-n'... was this simply a typo in the message or is it really like that when your tool generates that call? if it is not a typo, then it is possible that the passing on of the param doesn't succeed because of the missing space and so the '-n' is not detected and available to pass on...

Reply by email

Mattias Gaertner
to Seth Grover: Greetings. First off, congratulations on the 1.0 release. Lazarus is a terrific IDE and a…
Show quoted text 19 lines
Greetings. First off, congratulations on the 1.0 release. Lazarus is a terrific IDE and a great development platform. I've got a script that I use to build FPC/Lazarus from source and roll it into my own custom package. During the build of Lazarus, /etc/fpc.cfg doesn't exist yet. This isn't a problem for the most part, because I used samplecfg to generate an fpc.cfg file in a temporary location. Then, when building Lazarus, I do it like this: make bigide PP=/path/to/wherever/ppcx64 OPT="-n @/path/to/tmp/fpc.cfg" The -n tells it to not use the regular cfg paths, and what follows tells it where to find the cfg file to use. This works fine for most of the build: lazarus builds and links, as does startlazarus and some of the other binaries. However, when it gets to building the "lhelp" binary under chmhelp, I can see my OPTs aren't being passed down, and it fails with an error that /etc/fpc.cfg doesn't exist.

Fixed.

Mattias

Reply by email

Reinier Olislagers
to Seth Grover: Greetings. First off, congratulations on the 1.0 release. Lazarus is a terrific IDE and a…
Seth Grover wrote 5 lines
I've got a script that I use to build FPC/Lazarus from source and roll it into my own custom package. During the build of Lazarus, /etc/fpc.cfg doesn't exist yet. This isn't a problem for the most part, because I used samplecfg to generate an fpc.cfg file in a temporary location.

Once I used fpcmkcfg instead of samplecfg, I never looked back ;)

Just my 2 cents...

Regards,
Reinier

Reply by email

Sven Barth
to waldo kitty: i don't know if this ties in or not but your make line appears to be missing a space…
waldo kitty wrote 13 lines
On 9/4/2012 13:02, Seth Grover wrote: > > make bigide PP=/path/to/wherever/ppcx64 OPT="-n @/path/to/tmp/fpc.cfg" > > The -n tells it to not use the regular cfg paths, and what follows > tells it where to find the cfg file to use. i don't know if this ties in or not but your make line appears to be missing a space between the closing double-quote and the '-n'... was this simply a typo in the message or is it really like that when your tool generates that call? if it is not a typo, then it is possible that the passing on of the param doesn't succeed because of the missing space and so the '-n' is not detected and available to pass on...

The OPT argument is normally used in a way that a space is before and after it, so no need to pass a space manually.

Regards,
Sven

Reply by email