Skip to content

Documentation build fail #18

Open
Open
@Logarithmus

Description

@Logarithmus

It seems that documentation failed to build for 0.3.0:
https://docs.rs/crate/avrd/0.3.0

If you look at the build log, there's a panic with message "Read-only filesystem". I think it's docs.rs problem. But why 0.2.0 built successfully? Is it a regression?

Activity

dylanmckay

dylanmckay commented on May 14, 2020

@dylanmckay
Member

Read-only filesystem

That makes sense - crate currently generates .rs files for the MCU cores in the build.rs script ) (

avrd/build.rs

Line 29 in 3e75477

gen::all(&crate_root.join("src").join("gen"), &mcus).unwrap();
). It is discouraged to generate sources at runtime.

The best solution here would be to adapt the build.rs script into a script that can be run by the crate maintainers to update the autogenerated MCU core files so that they can be added into version control permanently. This will also make crate compilation much faster.

shepmaster

shepmaster commented on May 18, 2020

@shepmaster
Member

Plenty of crates Use build scripts to generate source code, so I don’t know why this would be a problem.

schulzch

schulzch commented on Aug 9, 2020

@schulzch

Plenty of crates Use build scripts to generate source code, so I don’t know why this would be a problem.

As far as I know, only OUT_DIR is writable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @shepmaster@schulzch@dylanmckay@Logarithmus

        Issue actions

          Documentation build fail · Issue #18 · avr-rust/avrd