I was reading on building FPC with debug enabled so I can trace into a unit and found that it was way too difficult to find the parameters. I know I had at one time edited the wiki page once I learned how to do it but to my surprise that info was either lost/moved or too hard to navigate and the search engines came up with too much information.

The build faq as a PDF on building FPC with the options and it never mentioned anything about adding DEBUG=1 to the make command. Presently I see -dDEBUG and -dRELEASE messages as fpc compiles itself. What is the propper way to take out the RELEASE directive?

Thanks

Andrew Brunner wrote

I was reading on building FPC with debug enabled so I can trace into a unit

make OPT="-O-" DEBUG=1 all

Jonas

Thanks, Jonas.

make OPT="-O-" DEBUG=1 all

When I ran this I see that both -dDEBUG and -dRELEASE are passed on the fpc command line. Is that correct?

Yes. It's what I saw. I was still able to trace database components line by line using Lazarus and GDB though.

Brian Winfrey wrote

> make OPT="-O-" DEBUG=1 all When I ran this I see that both -dDEBUG and -dRELEASE are passed on the fpc command line. Is that correct?

Yes.

Jonas

Op 2010-10-20 20:36, Jonas Maebe het geskryf:

Mind explaining why? DEBUG and RELEASE is known to be opposites, so what do you end up with when both defines are specified, a debug build (debug info includes) or a release build (stripped version - no debug info)?

Regards,
- Graeme -

The makefiles always pass RELEASE=1 (iirc). The later options on the command line will override the earlier ones, so OPT gets put somewhere at the end.

Henry

A debug build compiled for releasing (e.g., with all units compiled so that the compiler will not try recompiling them when it finds a source file with same name).

Jonas