• State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 21 subscribers
  • Views 4494 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Building Development Studio Projects in (Docker) Containers

rokelley

We have a small fleet of DS-5/Development Studio projects that target Cyclone V and we're interested in building these projects in containers. Some questions:

  • Our developers currently use Intel's ESW-DS-FIX node locked license. Is there a floating version of this? If not, what's the most cost effective alternative that will work with a container?
  • Is there a pre-existing container image that can build a DS-5/Dev Studio project by calling eclipse.exe in headless build mode?
  • For MSVC/Fortran/gcc, etc. we've started using tools like CMake instead of relying on the IDE for automated builds. Is there a similar toolchain in this area? Is eclipse in headless build mode the way to go?
Parents
  • 0 in reply to Ronan Synnott

    That does sound like it would do the trick, but due to the resulting image size/speed we ended up starting with an Ubuntu image and installing ARMDS and a specific version of the ARM compiler requested by the developers and that seems to be working well.

    Unfortunately, they appear to have been using a customized version of mkimage in the post-build step that was only built as a Windows exe years ago. I had installed the latest u-boot-tools apt package, but that was apparently generating an img file that had a checksum that didn't match prior builds of the same source.

    I was surprised (being new to ES) to find this article: https://www.rocketboards.org/foswiki/Documentation/BuildingBootloaderCycloneVAndArria10 where the instructions have you build u-boot from source.

Reply
  • 0 in reply to Ronan Synnott

    That does sound like it would do the trick, but due to the resulting image size/speed we ended up starting with an Ubuntu image and installing ARMDS and a specific version of the ARM compiler requested by the developers and that seems to be working well.

    Unfortunately, they appear to have been using a customized version of mkimage in the post-build step that was only built as a Windows exe years ago. I had installed the latest u-boot-tools apt package, but that was apparently generating an img file that had a checksum that didn't match prior builds of the same source.

    I was surprised (being new to ES) to find this article: https://www.rocketboards.org/foswiki/Documentation/BuildingBootloaderCycloneVAndArria10 where the instructions have you build u-boot from source.

Children
No data