Skip to content

Include support for either a base micro-architecture as default, or compile to suit an endpoints specific micro-architecture #26

@atheurer

Description

@atheurer

Having the default avoids having builds which don't work in some endpoints (controller built for newer CPU than the endpoint).

Supporting a micro-architecture means that

  1. we need to accurately identify what the micro-architecture of the endpoint is. We probably need to rely on gcc for this, as that is what's deciding what optimizations to use.
  2. We need to include the micro-architecture in the md5sum for the container image tag
  3. We might need to support running workshop on the endpoint, especially if the userenv is different (and have a different compiler version) and if the cpu architecture is completely different (or we have to cross-compile). This could also vastly speed up container builds if we have to build for many endpoints.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions