Skip to content

[windows] Bump ffigen to 16.1.0#2495

Closed
Levi-Lesches wants to merge 5 commits intoMaikuB:masterfrom
Levi-Lesches:windows-ffigen
Closed

[windows] Bump ffigen to 16.1.0#2495
Levi-Lesches wants to merge 5 commits intoMaikuB:masterfrom
Levi-Lesches:windows-ffigen

Conversation

@Levi-Lesches
Copy link
Contributor

@Levi-Lesches Levi-Lesches commented Dec 13, 2024

Closes #2471 by manually bumping, re-running ffigen, then cleaning up the resulting Dart code.

The big change in ffigen here is that it better handles enums, by generating actual Dart enums instead of integers

@Levi-Lesches
Copy link
Contributor Author

Levi-Lesches commented Dec 13, 2024

Well there you have it:

Because flutter_local_notifications_windows depends on ffigen >=15.0.0 which requires SDK version >=3.4.0 <4.0.0, version solving failed.

So to merge this, we'd have to bump the SDK to ^3.4.0 and Flutter ^3.22.0, which are the next versions of Dart and Flutter. It's not a terrible change, but this PR doesn't add any new functionality so it's also not a high priority.

Feel free to mark as a draft if you want to wait on this

@MaikuB
Copy link
Owner

MaikuB commented Jan 16, 2025

Happy to bump to Flutter 3.22 as that then makes the minimum Android API 21. #2440 is dependent on Flutter 3.22 as well but held off so that would allow Flutter 3.22 to be at least the two stable releases behind

@Levi-Lesches Levi-Lesches changed the title Update Windows code to ffigen v16 [windows] Bump ffigen to 16.1.0 Jan 16, 2025
@Levi-Lesches
Copy link
Contributor Author

Okay, confusingly, ffigen ^16.0.0 conflicts with Flutter 3.22 because of a conflict with the analyzer and meta packages. I've opened dart-lang/pub#4488 to discuss how this could be caught sooner because my computer, with the latest Flutter, doesn't show these issues. Not sure what to do except wait in this case.

@MaikuB
Copy link
Owner

MaikuB commented Feb 15, 2025

I've made the change to bump the Flutter version to 3.22 but ffigen 16 is looking to not be compatible with it so going to close this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants