Norman,
> > - kaplibs uses hlink to create an index of the html files, which
> > kaplibs then uses to create some html which allows clever searching of
> > the kaplibs prologues. This seems a legitimate reason for adding htx
> > as a
> > build (or should it be sourceset) dependency of kaplibs.
>
> ...that only kaplibs has a real need for hlink, since it uses the
> output for its own purposes. So kaplibs should declare a dependency on
> htx and have a STAR_CHECK_PROGS(hlink) in its configure.ac.
>
> If hlink is required for building the _distributed_ sources -- that is,
> for building the set of sources which are compiled into the distributed
> sourceset -- then htx should be a sourceset dependency.
So I suppose that means that htx should be a build dependency, not a
sourceset dependency, for kaplibs.
> So I vote that we don't bother with hlink in any standard macros,
> remove the call to it from ast and (very probably) echomop, and if we
> think it necessary just add a final hlink step to the `make world'
> rule, possibly via
>
> world: $(ALL_TARGETS)
> @HLINK@ ...
>
> How's that?
Do we not also need some way of hlinking documents as part of "make dist"?
When Bill Joye gets an ast-4.0.tar.gz he will not want to link the docs
himself (he is unlikely to have htx available anyway).
So should hlink not also be built into the "dist" target in addition to
the "world" target?
David
|