NetBurner Community Forum

Hi,

We have recently ported our application from NNDK 2.7.3 to NNDK 2.9.7.

Currently all of our development is done on Windows with NBEclipse. However we are looking to start building using the CLI, in particular within a Docker container.

I noticed this repo which seems to support building NNDK v3.X.X in a container on Linux. viewtopic.php?t=3249
However, I just want to check whether or not NNDK v2.X.X can be built similarly.


According to the NNDK release matrix for our platform (MOD5441X) it seems not. Would like to get your confirmation, and whether this means that a Windows docker container is required.

What is the reason that NNDK v2 is only for Windows/MAC? Is it because, at least for the Coldfire, the older m68k-elf-gnu cross-build tools are only available for those two operating systems?

Could you propose any alternatives for command-line based builds? We may or may not go ahead with making a Windows Docker container.

Thanks

So in a normal 2.9.7 install on windows you will find a setenv.bat file in the nburn root.
If you run that then you can build from the windows command line.
make
make clean
make load etc...

With 2.9.7 you have to make sure you also build in the system and platform/system directories as the make system does not maintain those after modification in those files.

I believe that you can do a linux install of 2.9.7. but to get support for that please submit a support request.

Hi. Thanks for the quick response.

NNDK v2.9.7 only has Windows and Mac releases, and I confirmed that their m68k-elf-gnu cross-build toolchains will NOT run on Linux (“Exec format error”). As a result, Linux Docker is not possible without more support.

If there is release of NNDK v2.X.X for Linux that is not available through support.netburner.com, that’s good to know. I’ll reach out to support for that.


As for builds using GNU Make…

I discovered that if I start a Makefile Project in NBEclipse, it will auto generate most of the Makefile for me. And that Makefile had have the system libraries linked in already. (Fortunately I don’t need to customize those… yet.) However, the object file rules and objcopy rule weren’t available in the the top-level makefile, so it was incomplete.

Thanks for your suggestion, it looks similar to this
https://www.netburner.com/NBDocs/Develo ... d3SVFhAX56
And this
https://www.netburner.com/learn/buildin ... ltyrfCyuNK

There are no official Makefile instructions for NNDK 2.X.X that I can find, but those look to be pretty similar to what you suggested.

I’ll try them out with the Makefiles in the nburn-examples directory just to start.

Thanks.

You can run 2.x or 3.x tools on your MOD54415, so you can move your code over to 3.x and then have a linux release. Are you trying to automate a build, or is it that you prefer to develop on your own linux machine?

Hi,

We would prefer not to move over to NNDK v3 after all because we would like to ensure that bug fixes and patches for one platform can be ported to our legacy platforms (like e.g. MOD5282) which don’t support NNDK v3.

We are trying to automate our builds in CI, and Docker would be preferable to avoid having to install NNDK tools on our CI agents. While it would be nice to build natively on Linux, the only reason for that was so that we could try to use the existing Dockerfile here
viewtopic.php?t=3249

As an alternative to nburn-docker, I am trying out a Windows Server Docker now. If it doesn’t work, I think it would not be a big problem for us to build natively on our CI agents after installing NNDK v2.

Hope that’s more clear.

Hi,

That makes sense to be backwards compatible. Please not the 5282 went EOL a year ago, so if that is the only other platform of concern it might be ok to got to 3.x.