NetBurner Community Forum

Does this only occur in a single project, or all of your projects?

Summary of Issues Compilation error when attempting to build in IPv4 only mode --- Compilation error when attempting to build in IPv4 only mode Known Affected Versions 3.5.1 Description A build error occurs when attempting to build an application with IPV4ONLY defined in nbrtos/include/predef.h . T...

Hello, I investigated this and it turns out that it was caused by a new issue, not a regression to the previous one you described. If you replace nbrtos/source/nbupdate.cpp with this attached update, it should be resolved. Note, we are working on a new release which should be available in the next w...

Hello, I looked through this and it looks like we failed to change the name of the global variable under the ENABLE_AUTOCERT_REGEN ifdefs. This internal variable name had been changed between the 3.5.0 and previous release. I fixed this for the upcoming release. You can fix it locally by renaming al...

There was a big change in the back end service between those two releases. The license method changed completely. I'm concerned that either your service or the configuration files did not get removed and you may be running portions of both versions. The new install should have uninstalled the previo...

Thanks for the note. Our installation process changed from 295 to 296, matching the same software we use in 3.x. It looks like the script that filled in this along with the copyright/revision tag on each source file did not make the transition. Since the release has already been out 2 weeks, I'm goi...

3.4 included big speed improvements for the ARM modules. The coldfire got marginally faster. For 3.4.1, we hope to include a speed boost for the coldfire as well. You can improve speed on the coldfire a little more by modifying some wolfSSL configuration options. To try this change, open user_settin...

Running the bat file is for command line. It sets the path for the current command line instance. The installer should have set up NNDK_ROOT as a system environment variable as well. Check your system env variables: From the start menu, search for Environment Vairables, and click on Edit the system ...

We use Docker extensively in testing our releases. I posted the Dockerfile that we use to test the NNDK so that others may use it as well. Its up on GitHub. The Dockerfile builds into a Linux installation of the NNDK with all required Linux utilities installed. If you are doing more then just testin...

Since 3.3.7, NBEclipse now includes it's own JRE, embedded within it's installation directory. For the 3.X tools, you don't need to modify any java system environment settings. For 2.X, it still needs a JRE 11 32-bit on the system path.