[frb] : Add support for Dart/Flutter bindings - Part II

[erdemyerebasmaz]

Closes #9

This PR adds Dart/Flutter packages their build tools & generates Dart bindings.

There's a lot of boilerplate code, to ease review process I'd suggest you to go over these scripts:

ls-sdk-flutter/
-packages/flutter_breez_liquid/ffigen.yaml
-packages/flutter_breez_liquid/android/CMakeLists.txt
-packages/flutter_breez_liquid/windows/CMakeLists.txt
-packages/flutter_breez_liquid/linux/CMakeLists.txt
-scripts/**
-flutter_rust_bridge.yml
-justfile
-melos.yaml

PR TODO:

• Explain the usages of
  • just & justfile scripts
  • Melos & it's build scripts
  • CMake scripts used for Android & Windows/Linux targets

---

Other changelist:

• Add min profile for ls-sdk-flutter scripts 6691553
• Add suitable crate-types are configured for target devices 66f6886
• [ls-sdk-bindings] Use LsSdkError from ls-sdk::error 57d1d0c

---

TODO:

• Apply rename changes
• Only compile ls-sdk-core with build scripts

[erdemyerebasmaz]

@ok300 @dangeross Rebased & applied all the renaming/folder structure changes then generated bindings. Please take another look.

Ross has suggested moving flutter out of libs under packages and I agree with the notion but it'll have to wait because Flutter directory consists of build tools & packages.

If we move the whole directory under packages, we'll have Dart & Flutter package live under:

/packages/flutter/packages/breez_liquid
/packages/flutter/packages/flutter_breez_liquid

which I find non-ideal.

If making a folder & package name distinction is compatible with build scripts, I'll move build scripts elsewhere and generate the libraries under:

/packages/dart/ # for breez_liquid, the Dart only package
/packages/flutter/ # for flutter_breez_liquid, the Flutter wrapper around Dart package

on a separate PR.

[ok300]

Looks good, just a few NITs about the project renaming

• a few instances of ls_sdk.* files
• a few instances of breez-sdk-liquid instead of breez-liquid-sdk

Might be worth to do a full search-replace to make sure all occurrences are covered.

[ok300]

I agree

/packages/dart/    # for breez_liquid, the Dart only package
/packages/flutter/ # for flutter_breez_liquid, the Flutter wrapper around Dart package

looks cleaner, if it's possible to achieve in a separate PR.

[erdemyerebasmaz]

Looks good, just a few NITs about the project renaming

• a few instances of ls_sdk.* files
• a few instances of breez-sdk-liquid instead of breez-liquid-sdk

Might be worth to do a full search-replace to make sure all occurrences are covered.

Thanks, I believe everything is covered now.

I agree

/packages/dart/    # for breez_liquid, the Dart only package
/packages/flutter/ # for flutter_breez_liquid, the Flutter wrapper around Dart package

looks cleaner, if it's possible to achieve in a separate PR.

Yes, I plan to handle it on a separate PR.

Current folder structure is made compatible with changes in #130