Yes - generally I run builds here with the asserts in, to catch unexpected behaviour. It makes everything slower though so I take them out for 'real' builds.
Having said that, in the last year or so Espruino has grown so large that I'm unable to build without release on most platforms.
Just fyi USE_CRYPTO=0 could be a bad idea - often makefiles/C files only check to see if a definition is made, not what it is. It might be that it actually has the same effect as USE_CRYPTO=1. If you don't want it, just leave out of the command line
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Yes - generally I run builds here with the asserts in, to catch unexpected behaviour. It makes everything slower though so I take them out for 'real' builds.
Having said that, in the last year or so Espruino has grown so large that I'm unable to build without release on most platforms.
Just fyi
USE_CRYPTO=0
could be a bad idea - often makefiles/C files only check to see if a definition is made, not what it is. It might be that it actually has the same effect asUSE_CRYPTO=1
. If you don't want it, just leave out of the command line