I solved this for me by organizing my projects so that their docs don't refer to each other in a circular way, and by organizing my builds so that the order of dependency is respected:
a (top-level, no intersphinx refs) b can refer to a c can refer to b and a Luc On 22/01/16 19:30, Ned Batchelder wrote: > At edX, we're using intersphinx to link among our own projects. But > it's designed to pull .inv files from readthedocs. This means if we add > a new reference between projects, the build will fail until the target > has been published. I tried using the second value in the mapping tuple > to point to a local file, but the file hadn't been created yet. > > Is there a way to generate all the .inv files in a first pass, and then > do the full build of the doc? > > --Ned. > > -- > You received this message because you are subscribed to the Google > Groups "sphinx-users" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to sphinx-users+unsubscr...@googlegroups.com > <mailto:sphinx-users+unsubscr...@googlegroups.com>. > To post to this group, send email to sphinx-users@googlegroups.com > <mailto:sphinx-users@googlegroups.com>. > Visit this group at https://groups.google.com/group/sphinx-users. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to sphinx-users+unsubscr...@googlegroups.com. To post to this group, send email to sphinx-users@googlegroups.com. Visit this group at https://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
