feat: add build hooks support to plugin template

[realmeylisdev]

Description

Adds optional build hooks support for compiling native code in the very_good_flutter_plugin template, enabling developers to quickly ramp up when their plugin includes native assets.

Closes #392

Changes

Core Changes

• ✨ Added use_build_hooks boolean variable to brick.yaml (defaults to false for backward compatibility)
• 📦 Added build hooks dependencies (hooks, code_assets, native_toolchain_c) to platform packages when enabled

Platform Support

Added build hooks to all native platforms:

• 🐧 Linux
• 🍎 macOS
• 🪟 Windows
• 📱 iOS
• 🤖 Android

Implementation

Each platform includes:

• hook/build.dart - Build hook script that compiles C code using CBuilder
• src/native_example.c - Example C function (add()) demonstrating FFI usage
• Updated pubspec.yaml with conditional dependencies

Documentation

• 📚 Added comprehensive README section explaining:
  • What build hooks are and their benefits
  • How to use the example native function
  • How to add more native code
  • Link to official Dart build hooks documentation

Benefits

✅ Quick Ramp Up: Developers can immediately start using native code with pre-configured build hooks
✅ Modern Best Practices: Uses the new stable build hooks system from Dart 3.10 / Flutter 3.38
✅ Complete Example: Working C code example shows the full FFI workflow
✅ Backward Compatible: Optional feature (off by default) doesn't affect existing workflows
✅ Multi-Platform: Consistent implementation across all native platforms

Testing

To test this feature:

1. Generate a plugin with build hooks enabled:

   very_good create flutter_plugin my_plugin --use_build_hooks true

2. The generated plugin will include build hooks infrastructure for compiling native code

3. Build the plugin to verify hooks execute correctly:

   cd my_plugin_linux
   dart run

Requirements

• ✅ All CI/CD checks are passing (to be verified by CI)
• ✅ There is no drop in test coverage percentage (to be verified by CI)

References

• Build hooks documentation: https://dart.dev/tools/hooks
• Flutter 3.38 & Dart 3.10 announcement: https://blog.flutter.dev/announcing-flutter-3-38-dart-3-10-building-the-future-of-apps-503429eeb685
• Native assets umbrella issue: ☂️ Build hooks & Code assets flutter/flutter#129757

[omartinma]

Thanks for the contribution @meylis1998, we will proceed with the review of this shortly!

[marcossevilla]

thanks for opening this PR! I'll take a closer look later today, in the meantime, can we leave upgrades to VGA for another PR?

[realmeylisdev]

Done! Removed the VGA upgrade from this PR and created a separate PR for it: #417

[marcossevilla]

will wait for @ryzizub to give his review by EOW in order to approve 👍

[realmeylisdev]

will wait for @ryzizub to give his review by EOW in order to approve 👍

@ryzizub inspired, encouraged to do all these. Huge thanks to him

[ryzizub]

Overally looks great! Good job, im just getting some dependency issues

[realmeylisdev]

@ryzizub feel free to review my other PRs. @marcossevilla reported that all others 'LGTM' too. Appreciate it!

[ryzizub]

Can we also use that hook assets in dart? I believe it would be awesome for example, since this way its now it can be easily left out

[realmeylisdev]

@marcossevilla please review!

[ryzizub]

@meylis1998 I was probably unclear on my comment.. sorry 💙, what i meant with Can we also use that hook assets in dart is using that hook add method inside the dart (for example like https://dart.dev/tools/hooks#reference-assets) . Cause right now is the hook method unused . Hope that makes sense!

[realmeylisdev]

@meylis1998 I was probably unclear on my comment.. sorry 💙, what i meant with Can we also use that hook assets in dart is using that hook add method inside the dart (for example like https://dart.dev/tools/hooks#reference-assets) . Cause right now is the hook method unused . Hope that makes sense!

Done! Added @Native bindings for the hook assets in 4afc8da.

[realmeylisdev]

Finally was able to get the CI checks right)

We can review it now.

[ryzizub]

@meylis1998 Great work on native bindings!! I would include add method to platform interface and use that binding on each platform side. That way on dart side we wont care about each platform but we will use the plugin itself.

So instead of
https://github.com/VeryGoodOpenSource/very_good_templates/pull/411/files#diff-fb58dfe143fc9c78540dcceb2e7800f9dbcfa1499e40e36d119365e2eaa84c83R31

We will use something like _platform. add in my_plugin :) Hope that makes sense

[realmeylisdev]

New Usage Pattern

// Before (platform-specific import)
import 'package:my_plugin_android/my_plugin_android.dart';
final result = add(24, 18);

// After (main plugin import)
import 'package:my_plugin/my_plugin.dart';
final result = add(24, 18);

[realmeylisdev]

Can't wait to see them merge.

[ryzizub]

Im getting also on generated plugin some format issues mainly Missing a newline at the end of the file.

I would recommend generating this template via mason and verify the code

[ryzizub]

I was testing this on package and i found issues one of them is that assetName should match the library URI where @Native is declared.
Can you verify that its properly running when the plugin is connected and add method is used?

[ryzizub]

@meylis1998 let me know if you need assistance to resolve issues

[marcossevilla]

@meylis1998 were you able to take a look at this?

[marcossevilla]

@ryzizub @realmeylisdev let me know if we can close this one for now or if we want to fix the issues