Hello!
Mariusz Zynel wrote:
I'm trying to link a program, that uses a couple of my own units already precompiled. So, I'm not specifying neither --automake nor --autobuild. Link editor ld reports error it can't find referenced symbols. There are two ways to go through this:
use autobuild facility - everything builds fine, or
supply object file names for gpc when linking - nightmare in case of advanced projects, though C works that way.
[...]
I didn't find that in documentation,
info -f gpc -n "GPC Options"
is it an unfixed bug?
No, it's a feature. But this is not the first time it is reported as a bug, so ...
On the other hand, Pascal units works different than C modules and special make tool is necessary. I remember Frank's posting on that. So, automake seems quite natural as default. Maybe there should be an option to turn it off instead?
GPC's current behaviour is due to consistency with other GNU compilers and with Borland Pascal where you also have to give an option `/M' in order to get the effect of `--automake'.
However if we agree on this list that `--automake' should be the default, I wouldn't mind changing GPC that way.
Another solution: It is planned to distribute an external utility in the future which does the same as `--automake' and more. This will make GPC's internal `--automake' facility obsolete.
What do you think?
E.g. Free Pascal works so that it always runs in autobuild mode, at least one of its older versions I had.
"Autobuild" or "automake"? I'd consider "autobuild" a bug, "automake" a feature.
Peter