You can try implement alternative version serial_port2 using binary_interop

[mezoni]

Today I added support of Windows 32/64 into binary_interop.
Now it support:

X86 Linux
X86 Windows
X86_64 Linux
X86_64 Windows

Mac OS X would be added soon.

More precisely binary_interop is cross-platform.
It is already ready for many other platforms.
Today I just update libffi_binaries package by adding two windows dll.
And voila, Windows are in the list of the platforms from where now possible call "C" code directly from Dart scripts ().

To add support of Mac OS X need only machine with Mac OS X for compilng the folowing files.

• libffi
• unsafe_extension

For the binary_interop they supplied (for supported platform) by other packages (two above listed).

This means that no need recompile anything once they installed if you call "C" code from Dart.
They are installed without any compilations on client machines.

Through the binary_interop you can load any dynamic libraries (system or supplied) and call native code directly from Dart.

This is only suggestion and I can try solve your problems with "C" language bindings.

[mezoni]

Forgotten to say that in binary interop you can forget about the memory allocation and freeing by hand.
Everything made automatically.
Until your variable does not garbage collected the your memory is hold.
I recommend declare them as final.

var t = new BinaryTypes();
final buffer = t["int"].array(500).alloc([]);

No need to call malloc. If variable is local memory will be freed when you leave the variable scope of code block.