Daco Harkes

Maybe xcodebuild can also consume a desired ios target version. Then we also want to plumb it through in `package:native_toolchain_c`.

> I haven't been able to get GDB working on my macbook LLDB is the Mac variant. > Is the [`package:ffi malloc`](https://pub.dev/documentation/ffi/latest/ffi/malloc-constant.html) the (presumably) `libc` `malloc` that `NSData` expects? https://github.com/dart-lang/native/blob/6a9282c7e2abd5d5ad89a2de1eb985ee9fc63262/pkgs/ffi/lib/src/allocation.dart#L15-L16...

> @dcharkes, I am wondering if down the line, instead of separate tool, this could be somehow integrated with native assets. That sounds amazing! Yes, maybe we can pull it...

I'm happy to let the project be in its own repo. (Unless there are some benefits to having it in this mono repo.) Maybe just a PR to another branch...

> You need to be an admin in both publishers to do a transfer. > They can invite you as admin, you do the transfer and then they can remove...

> @dcharkes is there any indication as to when native assets will be activated in a Flutter or Dart release without the flag? > > edit: sorry, I just saw...

> The fix for #835 is going to involve ffigen generating ObjC code for each block that the user needs. How would we solve the bundling of that ObjC code?...

Or can the Objective C just be compiled to a dylib and we can output it as a `NativeCodeAsset` @liamappelbe ?

> I'm not sure what the difference is between `ObjectiveCCodeAsset` and `NativeCodeAsset`, but the code can be bundled as an ordinary dylib. 👍 Then we don't need an `ObjectiveCCodeAsset`.

> Given that we won't run the link hooks sometimes, we probably want to have this available for `BuildConfig`s and `LinkConfig`s. This would mean for `CLinker` to implement `Builder` in...