Skip to content

Define <target-arch> for win32 and win64 #1439

Open

Description

@leamas

After starting building windows 64-bit builds OpenCPN/OpenCPN#2027 comes back to us again. In short, we don't define the target-arch metadata field in a consistent way.

This is not a practical problem at this point, but the data should be consistent in any case. In the case we start to build aarch64 windows plugins it will be crucial to get it right.

To my understanding, current situation is:

The solution seems simple: we should use x86 for 32-bit plugins and x86_64 for 64-bit. This will match other plugins, use the same xsd schemas and avoid bringing anything new into the ecosystem.

Unless there is more input I will file downstream bugs.

Activity

  1. bdbcat commented on Oct 23, 2026

    @bdbcat
    Member

    Ready to merge? We need a fresh build to get everyone up to current metadata definition.

  2. leamas commented on Oct 23, 2026

    @leamas
    ContributorAuthor

    This cannot be merged, this is an issue :)

    No hurry, really. We should give everyone a chance to catch up. Note that <target-arch> is not currently used by the core, we just adds it anyway. And as long as we do, it should be consistent.

    TL;DR; Everything works fine whatever target-arch is.

    EDIT: As long as my proposal holds, no changes are required in the xsd schemas.

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

      Issue actions