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).
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?
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?
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus