[X] I agree to follow this project's Code of Conduct
Current Behaviour
All libc doc references are broken since #121 , crate documentation does not make much sense anymore
Expected Behaviour
libc references should resolve to correct libc symbols.
Environment Information
irrelevant
Steps To Reproduce
No response
Implementation suggestion
We already utilize gdbstub feature for conditional dependency and doc generation, we should probably do the same for libc and find a way to ensure gdbstub and libc features are enabled when docs are generated by default
Is there an existing issue for this?
Code of Conduct
Current Behaviour
All
libc
doc references are broken since #121 , crate documentation does not make much sense anymoreExpected Behaviour
libc
references should resolve to correctlibc
symbols.Environment Information
irrelevant
Steps To Reproduce
No response
Implementation suggestion
We already utilize
gdbstub
feature for conditional dependency and doc generation, we should probably do the same forlibc
and find a way to ensuregdbstub
andlibc
features are enabled when docs are generated by default