Hi Peter,
I will look deeper into this. At first a glance, MacOS binaries seem to be incompatible with
proper ones (e.g. -f is a valid option for my readlink command).
he clan warning looks bogus (see end of README-11-bogus-compiler-warnings
as to how to fix this with ./configure.
The problem with Doxygen is this: if I run doxygen then I can read all
generated files with both firefox and with chromium - no problem.
If I then copy all files to some web server directory, then, depending
on both the web server and on the browser:
* neither chromium nor firefox renders them properly, or
* chromium renders them properly, but firefox does not (and complains
about CORS issues).
I suspect this either caused by the web server configuration and/or by how
doxygen works. If I browse the *savannah SVN repository* then chromium
renders the files properly, but firefox does not. If I browse the
*savannah git repository* (which uses a different wbb server setup) then
neither firefox nor chromium renders the files properly. In both cases all
Doxygen files are present.
Best regards,
Jürgen
On 10/18/22 8:03 PM, Peter Teeson wrote:
Hi Jürgen:
Thanks for the latest svn 1603. We still have issues. Log file attached.
E.G. Note lines 307, 336 et seq, 649 et seq, 741 et seq, ….
respect
Peter
P.S. In the past I was able to use Firefox to examine the Doxygen generated html files….
When we have dealt with the present issues I will run Doxygen and check what happens.