On 2020-04-14T07:53:32 +0200 Tim Verbelen via osgi-dev <osgi-dev@mail.osgi.org> wrote:
> Hi Chris, Mark > > The beauty of the requirement-capability system is that you can easily > define these requirements and capabilities yourself, in addition to the > Bundle-NativeCode header (which is translated to a requirement anyway). > > Also, the full list of arch strings can be found at > https://www.osgi.org/developer/specifications/reference/#ReferenceOS Hello! Possibly a slight misunderstanding here: The issue isn't that I need to pick a string for my own usage. The issue is that, as a library author, I need to use _a string that matches what other people are using_. Due to a lack of standardization, there may not actually be any agreement here. Worse, the end-user of the bundle only gets to pick once (via setting os.arch) so if two bundles want to see different strings, one of them is going to fail to resolve. I did a bit of investigating, and it appears that OpenJDK builds use "arm" and "aarch64": https://github.com/AdoptOpenJDK/openjdk-jdk14u/blob/master/make/autoconf/platform.m4#L57 But in the past (according to LWJGL developers), JVMs have also used all of the following: arm arm32 armv6 armv7 aarch64 armv8 -- Mark Raynsford | https://www.io7m.com
pgpA9vREH8UQk.pgp
Description: OpenPGP digital signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
