Skip to content

CI: Change doc generation to use a more generic target #54

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

Merged
merged 3 commits into from
Feb 4, 2025
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/docs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,9 @@ jobs:
working-directory: zephyr-lang-rust
run: |
# Note that the above build doesn't set Zephyrbase, so we'll need to do that here.
west build -t rustdoc -b nrf52840dk/nrf52840 docgen
west build -t rustdoc -b qemu_cortex_m3 docgen
mkdir rustdocs
mv build/rust/target/thumbv7em-none-eabi/doc rustdocs/nostd
mv build/rust/target/thumbv7m-none-eabi/doc rustdocs/nostd
cp docs/top-index.html rustdocs/index.html

- name: Build build documentation
Expand Down
2 changes: 2 additions & 0 deletions zephyr/src/sys/thread.rs
Original file line number Diff line number Diff line change
Expand Up @@ -233,6 +233,8 @@ impl Thread {
/// Safe use follows similar requirements to using this safely from within C code. Passing Rust
/// values through this interface is difficult to get right, and it is generally recommended to
/// use [`spawn`].
///
/// [`spawn`]: Self::spawn
pub unsafe fn simple_spawn(
mut self,
child: k_thread_entry_t,
Expand Down