You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 core does not currently care about target-arch for windows, be it 32 or 64 bits.
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.
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.
Activity
bdbcat commentedon Oct 23, 2026
Ready to merge? We need a fresh build to get everyone up to current metadata definition.
leamas commentedon Oct 23, 2026
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.