Replies: 2 comments 3 replies
-
I'm not familiar with nmake (other than what I just looked at in the docs) but this seems like a good approach to try first. Hopefully the nmake file ends up being easy to generate from the current Makefile. You could also try writing a In the end, the final versions of the docs will be built on Github Actions using Ubuntu-latest, so the ability to build the docs on Windows is really only important in so far as it helps you in the development cycle. If you can manage the development cycle by building + viewing the notebook version of the *.py file using jupytext directly, that's probably good enough. |
Beta Was this translation helpful? Give feedback.
-
I just wanted to note that when I was messing around with this earlier I discovered that it isn't an issue with making the actual .ipynb files. I was able to do this manually (i.e. jupytext --to ipynb --execute tutorials*.py), from the ./docs/ directory. Once doing this, the make file had no issue with compiling the docs for all the tutorials. I will look into what may be causing the makefile to not run this command when executing. |
Beta Was this translation helpful? Give feedback.
-
So I'm just going to bring the discussion from my pull request over to here since I think that the issue may be universal. So Windows can't natively run make and makefiles and instead has to use nmake and the file that goes with that. I came across a solution to install a make for windows function using chocolatey here and now I can use the make command natively but I'm still facing the same issue as before that when I run make html it still returns, for every single tutorial:
E:\robert\Documents\GitHub\MPoL\docs\index.rst:33: WARNING: toctree contains reference to nonexisting document 'tutorials/_____'
I think for my next step I'll try making a version of the makefiles that are the windows compatible ones and see if it works then, if so maybe it'll be possible to just include both.
Beta Was this translation helpful? Give feedback.
All reactions