On 2026-02-10 17:16, mailinglists--- via fpc-pascal wrote:
On 2026-02-10 15:32, Tomas Hajny via fpc-pascal wrote:
Hi Graeme,
Sorry for a silly question, but is the new release source-code
release only, or are there precompiled binaries (e.g. of DocView) as
well?
There's been a slight delay on updating the website. Based on previous
download
statistics, hardly anyone downloaded binaries, so it's source-code
releases only.
If the demand changes, I can revisit this again.
.
.
OK, no problem with that. I downloaded the source code and checked for
documentation for building. I found this documentation for building
fpGUI (for different scenarios like PasBuild, Lazarus, FP IDE and partly
also the command line FPC). Personally, I'd use the command line
version, but that focuses only building of individual example units,
thus not directly usable for DocView (see my original question above)
without previously building fpGUI. Considering your announcement of
PasBuild, I considered that to be the preferred solution. The directions
for building using PasBuild didn't mention anything about DocView
specifically - and indeed, using the command suggested to be used for
build using PasBuild didn't even touch DocView. I tried to find any
documentation specific for building DocView in the docview folder, but
couldn't find anything there. Finally, I found that building it using
"fpc @extrafpc.cfg docview.lpr" worked (after the previous fpGUI
compilation using PasBuild), but a bit more specific information might
be useful (especially considering that e.g. the included docdump tool
cannot be compiled that way - I found how to compile that one as well,
not really difficult from technical point of view, just mentioning that
it might a be a bit more user friendly).
Apart from that, I found strange/unwanted artifacts with the DocView
version compiled this way and running under MS Windows. I guess that
they're probably related to fpGUI rather than DocView itself - as an
example, the "OK" button in the "About" dialogue windows misses the
upper line until pressed and the vertical lines used in the included
ESC.INF file are not connected any longer (unlike with the latest
precompiled DocView version 1.4).
In addition, I noticed that the new version of DocView doesn't provide
the opportunity to specify the document codepage (previously available
in version 1.4, although with a limited set of options - however, that
could be extended). That is not necessarily good - I know that the
codepage information might be available in the INF file itself (or that
one could have specified it on the IPFC command-line), but IPFC had a
very limited set of supported codepages, thus the real codepage used for
a particular document might be different from the one specified in the
header of that document. I didn't have the possibility to check what
happens if opening such documents in the latest DocView, but I suspect
that it might not work very well...
Tomas
_______________________________________________
fpc-pascal maillist - [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
