-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doxygen2man #388
Doxygen2man #388
Conversation
This is in here from kronosnet so it cna be used by other parts of the cluster stack.
Signed-off-by: Fabio M. Di Nitto <[email protected]>
Signed-off-by: Fabio M. Di Nitto <[email protected]>
Signed-off-by: Fabio M. Di Nitto <[email protected]>
Signed-off-by: Fabio M. Di Nitto <[email protected]>
@wferi I have been talking with @chrissie-c on IRC and here is the summary: the current build system allows to do normal and cross-compile build as-is. Once the man pages for libqb will be auto-generated by doxygen2man, people doing normal builds will not notice any difference. People performing cross-compilation have 2 options:
This way we limit the 2 phase bootstrap of libqb only for people doing cross-compilation, that is a minority of the use base, without creating extreme complexity for people doing normal builds. The infra is in place, just need to extend as we kill hardcoded man pages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. I think it's ready to go in now.
ACK
Should this really be installed along with the library though? Seems a bit out of place for libqb to install a doxygen-related tool. |
See the discussion on #387 which led to this one |
And that it is part of the libqb-repo doesn't necessarily mean you would have to package it together with the library so that it would be installed on every production cluster. |
In Fedora, it has its own package. |
No description provided.