Skip to content

Improve Message Generation Documentation #401

Open
@maspe36

Description

@maspe36
Collaborator

Currently, our message generation pipeline is quite complex. Its complex, mainly because Rust does not have a stable ABI, and wants to compile all of the source code and dependencies source code, when compiling a crate.

We need to start documenting all of the various repositories and their responsibilities as it pertains to our message generation, in one place, in this repo.

I have some local notes I can upload in a few days that could potentially be used as a starting point.

Activity

changed the title [-]Improved Message Generation Documentation[/-] [+]Improve Message Generation Documentation[/+] on May 13, 2024
maspe36

maspe36 commented on Oct 13, 2024

@maspe36
CollaboratorAuthor

There is a really nice starting point being added in #417. We should expand this to cover the various build tools and their responsibilities with actually building the generated rust message code.

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

        @maspe36

        Issue actions

          Improve Message Generation Documentation · Issue #401 · ros2-rust/ros2_rust