Accept "ZEPHYR_MODULES" For Building Docs

RE: Accept "ZEPHYR_MODULES" For Building Docs

vindicator — Tue, 14 Dec 2021 15:54:18 GMT

Not yet. I resolve one thing and find something else ugly underneath.

I'm currently at your "merge_search_indexes.py:for src_name, src_value in src_object.items()" where it says "AttributeError: 'list' object has no attribute 'items'". Yet, when I "print("src_prefix", src_prefix, "src_object", src_object)", there's a BOATLOAD of "items" like "[[153, 0, 1, 'c.BITMASK_BYTES_CALCULATE', 'BITMASK_BYTES_CALCULATE'],..."

It's why I'm not marking my previous post as an "accepted solution" when it isn't yet since I'm finding there's more to it.

Python isn't my go-to language (goto pun?), so it's going to take a bit.

EDIT0: It "MAY" be the fact that "src_prefix" is blank/empty, in which case, I have to walkback through how that happened.

RE: Accept "ZEPHYR_MODULES" For Building Docs

ovrebekk — Tue, 14 Dec 2021 09:03:32 GMT

Were you able to get this working?

Unfortunately we only support building the docs as described in the documentation, using the standard folder structure.

Best regards
Torbjørn

RE: Accept "ZEPHYR_MODULES" For Building Docs

vindicator — Mon, 13 Dec 2021 16:17:38 GMT

docs.zephyrproject.org/.../manifest.html

EDIT0: Or rather that, along with changing paths as needed in sdk-nrf/west.yml

EDIT1: Along with setting the paths for zephyr and sdk-nrf, I also have to set the paths for the "Projects" and just go ahead and remove un(needed/wanted) "Projects" such as "hal_cypress".

It also looks like "conf.py" is expecting a project root dir that is NOT topdir, so I can't have projects like trusted-firmware-m in topdir, but some other dir within topdir like "modules" (commonly used) or I figure in my case, I'll just name it "Projects" to coincide with the west.yml tree.