But running is not enough :slightly_smiling_face: ...
# kotlin-native
o
But running is not enough 🙂 It needs to work with appropriate SDK, integrate with tools (like flashing), etc. I don’t think there is an open standard for everything, so that would take time and probably vendors coordination, or community effort. And this normally take a lot of time…
n
I feel like this would be an issue solved by whatever build system konan ends up using. An example of this would be something like platform.io which has multiple targets; the build tool tells it what cross compiler and uploader to use.
o
Build system is not enough for an IDE. It needs to know where symbols are and how they are encoded (library format), what is debug info and how to set a breakpoint, lots of stuff.
E.g. there is http://www.dwarfstd.org/ which we currently support, but who knows if embedded toolchain works with? Or even how to connect to remote device for monitoring/debugging/deploying… these are all custom solutions, AFAIK
n
Ah good point. I didn’t think about the debugger. 😕