On Wed, Dec 27, 2023 at 10:21:08PM +0100, Ralf Hemmecke wrote:
> > > Are you saying that
> > >
> > > ================
> > > ${GEN_VIEWPORTFILES_PHT}: %.pht: %.ht ${INPUT_EXTRA_INPUT} ${SMAN} \
> > > $(fricas_target_bindir)/hypertex$(EXEEXT) stamp-initial-ht-db
> > > echo $<
> > > unset DAASE; HTPATH=.; export HTPATH; \
> > > FRICAS_INITFILE='' ${XVFB} ${SMAN} -noihere -paste $<
> > >
> > > mobius.VIEW: ${inputsrcdir}/mobius.input
> > > (unset DAASE; FRICAS=${FRICAS}; export FRICAS; \
> > > FRICAS_INITFILE='' ${XVFB} \
> > > ${FRICAS}/bin/fricas -noht -noclef -eval ')read $<')
> > > ===============
> > >
> > > in src/doc/Makefile.in needs src/doc/ht/util.ht?
> >
> > Well, first rule needs 'util.ht'. I did not check which one.
> > 'mobius.VIEW' can be generated without using 'util.ht'.
>
> That is true according to the rules that are currently in
> src/doc/Makefile.in. However, I've just built fricas,
If you have xvfb, then build already generated images (more precisely
.xpm files). .xpm files are generated by cooperation of FriCASsys
and graphis and in this sense do not need 'util.ht'. But commands
to FriCASsys are sent from HyperDoc and HyperDoc needs macros from
'util.ht' to do this. In other words, generating .xpm files is
a byproduct of normal generation of HyperDoc pages which needs
'util.ht'.
> then removed util.ht
> from the build directory and also from the source directory. Additionally I
> remove "util" from the line in Makefile (in the build directory) that
> corresponds to
>
> https://github.com/fricas/fricas/blob/master/src/doc/Makefile.in#L237
>
> Then said "cd src/doc; make book.pdf" and got book.pdf with all generated
> pictures.
In this stage you merely convert .xpm files to .ps.
> I could change Makefile.in to make it really independent of util.ht.
> In fact, now that we discuss about it. Since it is actually a style file for
> hyperdoc, it *is* in that sense special. I only left it under src/doc to
> keep all .ht files together. When I developed the build machinery for
> book.pdf, I had no idea about what was used where.
Generating HyperDoc pages is documented, so all needed to do
this must be available in shipped tarball. So we need to copy
util.ht from source location to destination. Assuming that we
always use 'util.ht' from target tree its exact location in
source tree is not that important. But it makes sense to keep
it together with other .ht files. If somewhere we use 'util.ht'
from source tree, then this is a bit unclean, but normally they
are the same so not too bad.
And 'util.ht' is not so special: you can define macros in normal
files but normally we want to share macros for all files, so
we put them in a common place. And changing HyperDoc pages
may need new macro, so it is really better to keep them together.
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/ZYyxpA_iqMdUzb3P%40fricas.org.
