Is there any particular reason that headers from the OGSF library reside
with the source and then are copied to "include/" after compilation?
Shouldn't they be moved to "include/" and left there like has happened
with other libraries? I don't see any automatic header file generation
that would preclude from doing so.
--
Brad Douglas <rez touchofmadness com> KB8UYR
Address: 37.493,-121.924 / WGS84 National Map Corps #TNMC-3785
Brad Douglas wrote:
Is there any particular reason that headers from the OGSF library reside
with the source and then are copied to "include/" after compilation?
AFAICT, no.
Shouldn't they be moved to "include/" and left there like has happened
with other libraries?
Probably.
I don't see any automatic header file generation that would preclude
from doing so.
local_proto.h gets renamed to ogsf_proto.h during the installation,
and gstypes.h is modified accordingly. But that's trivial to change.
--
Glynn Clements <glynn@gclements.plus.com>