Re: The portable way to find nimbase.h or system.nim location

This does not seem to work for compilers installed via choosenim. When I compile nim code for embedded systems using the compilers from platformio, all I need a pointer to the location of nimbase.h. It would be ideal if choosenim could update a symlink (or similar) in a standard place so I don'

Re: Nim microbit

No, I never tried using nim strings or anything involving heap storage at all. Most of the embedded systems I have worked on never had such luxuries anyway, so I instinctively declared all my variables statically and had no such problems... Here are the nim flags I used, just in case they are r

Re: Nim microbit

I played around with writing nim code for tiny systems (including a micro:bit) several months ago. Here are some of the key strategies I learned along the way: * check out [https://platformio.org](https://platformio.org) This tool knows all about building software for a wide range of embedded

Re: Strange problems with --os:standalone --gc:stack

PROBLEM SOLVED! The garbage collector is innocent. When using --os:standalone, you must provide a file panicoverride.nim. I wanted to prettify my output_message, so I imported another module (which contained the asserts etc.) in to panicoverride. It seems that the panicoverride code is processe

Re: Strange problems with --os:standalone --gc:stack

Oops, I should have said that my project (a few thousand lines of nim code) already compiles without errors using --os:standalone and --gc:none. It was only after changing to --gc:stack that I had to spend half an hour or so hacking my code around to compile successfully again. Okay, if I manag

Strange problems with --os:standalone --gc:stack

I came across [