[Lazarus] Basic chm help creator (LHelpCreator)

[Žilvinas Ledas]

On Mon, 07 Jun 2010 17:05:17 +0000
Mark Morgan Lloyd <markMLl.lazarus at telemetry.co.uk> wrote:

> Over the last couple of days I've partially regressed and now have 
> lazarus-stable and lazarus-oldstable directories containing 0.9.28.3 and 
> 0.9.26.2. I found that I needed to build these with FPC 2.4.0 and 2.2.4 
> respectively, so I have put copies of the fpc binary and fpcsrc 
> directory in /usr/local/lib/fpc/x.y.z/.
> 
> In general this appears to work, but I noted that I had to change the 
> "Compiler path" and "FPC source directory" settings in the "IDE Options" 
> screen to track the FPC version (although I could obviously also use 
> multiple configuration files).

Yes. I guess that's better for this case.

 
> I find that the "FPC source directory" setting appears to accept a macro 
> $FPCVer(), but the "Compiler path" does not. Irrespective of whether 
> what I'm trying to do is crazy, am I missing anything obvious?

Yes. The FPCVer macro gets the fpc version from the compiler.

 
> If the above is correct, then the "IDE Options" screen appears to accept 
> options in the format $FPCVer(), while the "Project Options" -> "Target 
> file name" expects e.g. $(TargetCPU). Similarly the "External tools" -> 
> "Edit tool" form suggests that different forms are supported, and in 
> particular I notice that it refers to $TargetCPU().
> 
> Are two different macro forms still required, and can this ever be 
> cleaned up?

Both formats are accepted. 
The format $Name(Parameters) is used for macro functions.
The format $(Name) indicates a macro variable.

See here:
http://wiki.lazarus.freepascal.org/IDE_Macros_in_paths_and_filenames

Mattias