Skip to content

[macOS] Regeneration of bridgesupport files necessary #3447

Description

@HeikoKlare

The bridge support files for macOS used to be regenerated for newer macOS SDK versions. This has not happened for quite a while and we have started to manually add entries for newer macOS SDKs to that file so that we can use the MacGenerator for JNI binding generation on new API.

I have tried to regenerate those files with the available documentation (in particular the according readme) but the results look quite different from what we have right now (different properties due to using aarch64 and a high number of changes), which then lead to the MacGenerator deriving code that has many compile errors.

We should thus do the regeneration of those files in a separate task including the necessary cleanup and maybe MacGenerator adaptations to be conforming with latest SDK versions and have fully auto-generated bridgesupport files again.

Originally from @Phillipus: #3435 (comment)

Looking at the following:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=502090
https://bugs.eclipse.org/bugs/show_bug.cgi?id=514191
https://github.com/eclipse-platform/eclipse.platform.swt/blob/master/bundles/org.eclipse.swt/Readme.macOS.md

It seems that there have been times when there was a macOS version update where all the bridge support files > have been completely regenerated against a new macOS SDK. The last time was here:

b51b906

Metadata

Metadata

Assignees

No one assigned

    Labels

    macOShappens on macOS

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions