Re: [docs] what is purpose of "$(O)" in top-level docs Makefile?
Quentin Schulz <[email protected]>
| Newsgroups | org.yoctoproject.lists.docs |
|---|---|
| Message-ID | <[email protected]> |
Hi Robert, On 8/20/26 12:52 PM, Robert P. J. Day via lists.yoctoproject.org wrote: > > almost certainly a dumb question but was perusing the top-level docs > Makefile and read at the bottom: > > > # Catch-all target: route all unknown targets to Sphinx using the new > # "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS). > %: > $(SOURCEDIR)/set_versions.py > @$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O) > > it's unclear to me what the point of $(O) is if it's supposed to be > a "shortcut" for $(SPHINXOPTS) when they're both incorporated in that > build command. can someone clarify what is going on here? > Introducing commit from 6 years ago doesn't clarify anything, so, no. It's there, doesn't hurt and we don't know if it's used, so... /me shrugs. We could remove the misleading comment though. Cheers, Quentin