Closed Jakuje closed 6 months ago
Exact.
Generating the doxygen.conf
file will not be enough.
I generate the documentation using make doxygen
and this will not work with meson.
What "more standard way" are you thinking about?
This would be enough for the way how we do it in Fedora package now as we run doxygen directly during build:
https://src.fedoraproject.org/rpms/pcsc-lite/blob/rawhide/f/pcsc-lite.spec#_104
By standard way I meant checking the doxygen presence in meson and creating the API docs as part of meson build, by default or with specific target.
Done in https://github.com/LudovicRousseau/PCSC/commit/a217c5c52d6568c997c351ad3d8633e8aa4a2ec2
Do you think meson should also install the documentation? If yes where?
Thanks! The change looks good to me.
Regarding to the installation, the fedora package pushes them into /usr/share/doc/pcsc-lite-doc/api
, which is basically what the build system passes to meson as --datadir
+ /doc/
+ package name, so I would consider this distribution dependent and not install it (Fedora macro %doc
copies the files from build root to the proper location).
I did not know the pcsc-lite-doc fedora package.
On my side. I generate the documentation to populate the web site https://pcsclite.apdu.fr/api/
When building the latest version 2.2.0 with meson, I do not get
doxygen.conf
generated fromdoxygen.conf.in
causing Fedora build to fail as we use that one to gerenate doc supbackage.It should be just matter of passing it to
configure_file
(maybe under the conditional for generating separate docs?). Something like this works already:Its question if it makes sense to keep it like this or we want to allow building the docs in some more standard way than calling
doxygen
from spec file directly.