Skip to content
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

Usage with breathe? #44

Open
mgiaco opened this issue Jul 12, 2017 · 2 comments
Open

Usage with breathe? #44

mgiaco opened this issue Jul 12, 2017 · 2 comments

Comments

@mgiaco
Copy link

mgiaco commented Jul 12, 2017

Hello,

I use sphinx in combination with https://github.com/michaeljones/breathe. So the build works now but my problem is that breath use the xml output from doxygen also in the sphinx html output. When I run your extension i also updated my sphinx build in a way that doxygen is builded before. But the problem is that the xml folder is not gathered by the sphinxcontrib-versioning. Can I set a path which should also be copied or so? So it is like a static folder but is also generated on the fly.

@mgiaco
Copy link
Author

mgiaco commented Jul 12, 2017

So now i found out that the path is the problem. When I build my project with this extension I generate the doxygen output on a relative path. But the extension build the sphinx on a special path User/local/Temp/.....
And then the doxygen xml output is never found by the sphinx/breathe build. How can I get that path where the build happens? os.getcwd() did not work because the running path is the project path but the extension does some special path switching. Why does the extension do not build in the project tree?

The only workaround I think is committing the doxygen xml output but that isn't really nice I think.

@plauche
Copy link

plauche commented Feb 28, 2018

@Robpol86 any suggestions on how to work around this? I've run into the same issue. I looked at moving my doxygen generation into the conf.py but it looks like that is executed prior to sphinx-versioning creating a temp dir and moving there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants