Quote:
Originally Posted by NiLuJe
should still be considered a WIP, it's only been tested on a few different devices, and we don't really have time to offer real support for it.
|
I get the idea, and understand that the involved devs don't want to be flooded with too much noise around well known early prototype shortcomings.
However, it's also a missed chance to get early feedback around the most wished features/bugs from a larger user base.
Quote:
Originally Posted by NiLuJe
I *have* tried to make sure the doc steers people towards koxtoolchain, so any and all feedback on that front if you hit a snag along the way would be appreciated  . |
Thinking it over again I think this is one of the rare occasions where I managed to compile c code. And I have failed in many other attempts. So the build is already very mature. I especially liked the responsive feedback and parameter exposure. So thanks for the good work.
I think, that it would have helped a little to have a shorter readme with fewer words, but the most recommended build/release commands at top. Including the commands to use koxtoolchain. ... and then following with the details later what it does and why we do it that way. Just give the user first what he needs want's to know first ... there has been a lot of smart good guidance on this in here:
https://www.americanscientist.org/bl...ntific-writing
I'll try to fire a simple PR if I can make this more concrete.
Another idea would be to share a docker image with the koxtoolchain. On my weak consumer laptop the build process cost me around almost 30 mins. And I failed in the first attempt to run it as I have started the process on a disk with almost no space on it ;-)
... with the toolchain ready and in a container I don't have to dive into the topic and can just re-use the output of a smart build.