-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
mkdoxy custom output path #108
Comments
Hello @JakubAndrysek If you have some time, could you please take a look at it? |
Hi, sorry for the delay; I didn't have time for my open-source project. I have tested https://github.com/JakubAndrysek/MkDoxy-demo project that contains After installing dependencies, everything works perfectly. save-apiImportant note - The Please try it without a custom doxygen folder - it is a new feature and might contain unexpected problems. |
You have to configure the nav output by yourself as you mentioned in the image before. nav:
- 'Doxygen':
- 'Doxygen-Demo': 'doxygen-demo/**' This won`t export the output as you want. Automatically generate NAV menuThis is not supported yet - #40 |
Thank you so much @JakubAndrysek for the response. I'll try following what you suggested. I hope it works 🤞, if not I'll have to get back to you again 😀 |
Hello @JakubAndrysek , Thanks for this wonderful plugin. I am trying to render output of mkdoxy through dev container. I want to store and see the output files in a custom folder, tried adding
save-api
function but somehow i am not able to see the folder.My mkdoxy config looks like this -
DOXYFILE -->
Surprisingly, when i do
mkdocs build
.site/doxygen-demo
site/assets/.doxy/doxygen-demo/doxygen-demo
FYI
doxygen-demo == <NAME-OF-PROJECT>
Also If even after this works, is the addition of output files in nav section in mkdocs.yml a manual process?
will the following work in my case?
Thanks!! Any ideas to resolve this?
The text was updated successfully, but these errors were encountered: