Replies: 2 comments 1 reply
-
The main purpose of the xPack project was to automate CI builds and tests. Eclipse and VSCode do not fit very well into this category.
That would require a lot of maintenance efforts, since there are a lot of releases. Plus that the binaries might not be standalone and relocatable, as all other xPack binaries. But if you need the J-Link tools as an xpm dependency (or any other tools), you can create your own GitHub project and refer to the Segger URLs in |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! For myself doing CI builds I just use Docker, which is very easy and repeatable. I have one code base, and one target processor, so the CI process is very easy and simple without xPacks. As such xPacks has little value in the CI process for me personally. The harder thing I find is dealing with multiple developers and making it where they can develop code and have repeatable build environment for each developer on windows with an IDE. Talking with other embedded developers it appears that many of them ship a virtual box image of windows OS with all the development tools installed and working with their projects to get around this problem. They then run into problems of how to store the virtual box image and maintain it, however to date none of them have a better solution. I am going to recommend moving to Segger Embedded Studio for our needs. It might be expensive, but it solves the problem of repeatable build environment on windows with an IDE. Thanks |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I it possible to have xPacks install eclipse or VSCode? How about Segger JLink tools?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions