Replies: 7 comments 8 replies
-
I think that is the idea set out in https://eclipse-embed-cdt.github.io/templates/hello-world-qemu-xpack/ - not sure if anything is missing to make it complete. |
Beta Was this translation helpful? Give feedback.
-
Yes, that's exactly the point with xPacks, to provide a reproducible development environment. The recent Embedded CDT plug-ins added the option to prefer the tools installed in As Jonah mentioned, this configuration is already used by the projects created via the Hello World QEMU template. However, you don't have to use the template, you can manually run Then you save the The nice thing is that this works on any platform (Windows, macOS, Linux). |
Beta Was this translation helpful? Give feedback.
-
It would be nice if/when eclipse can not find compiler or tools and the
project has a package.json it would either automatically run xpm install or
ask user if they want to run the install.
I am finding the technical overhead required for many developers to open
terminal and type xpm install is too difficult. That is they expect they
can download project double click on project file and everything will
magically work.
I can understand this desire since many IDEs appear to do this it is.
xPacks is a great tool for the job!
Thanks
Trampas
…On Thu, Aug 24, 2023, 5:43 PM Liviu Ionescu ***@***.***> wrote:
Yes, that's exactly the point with xPacks, to provide a reproducible
development environment.
The recent Embedded CDT plug-ins added the option to prefer the tools
installed in xpacks/.bin to those installed in the traditional locations
(there is a button in the project settings).
As Jonah mentioned, this configuration is already used by the projects
created via the Hello World QEMU template.
However, you don't have to use the template, you can manually run xpm init
to add a package.json to your project, and install the binary tools by
invoking xpm install @xpack-dev-tool/xxx in the project folder.
Then you save the package.json to your repo; someone else can clone it,
and invoke xpm install in the project folder to get exactly the same
tools as you did originally.
The nice thing is that this works on any platform (Windows, macOS, Linux).
—
Reply to this email directly, view it on GitHub
<#587 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUHSPOV7FHRRHJBSU2SBWDXW7DIXANCNFSM6AAAAAA35TFNDE>
.
You are receiving this because you authored the thread.Message ID:
<eclipse-embed-cdt/eclipse-plugins/repo-discussions/587/comments/6817366@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
Please do not reply by email, but use the web interface. Or, at least, do not quote back the entire message. See this.
:-( Given the need to install node/npm/xpm, your desire to avoid the terminal entirely is not realistic. However, once these tools are installed, it is possible to add a menu entry to invoke |
Beta Was this translation helpful? Give feedback.
-
Just to be accurate, Eclipse does not use xPacks.
FWIW I found Inno Setup easy to use for Windows installers. |
Beta Was this translation helpful? Give feedback.
-
The Eclipse Ecosystem already provides an embedded (shipped as Eclipse Plugins in a p2 site) of the node runtime that we can integrate. See https://github.com/eclipse-wildwebdeveloper/wildwebdeveloper/tree/master/org.eclipse.wildwebdeveloper.embedder.node for the guide. That should allow the bootstrapping of xpm from within Eclipse entirely with no additional tool installation required. Similar to how other node dependent packages in the Eclipse ecosystem work, the xpm installtion can be done at "our" build time. |
Beta Was this translation helpful? Give feedback.
-
Erich Styger is appearing to have similar issues: Conda looks like an interesting alternative to xPacks |
Beta Was this translation helpful? Give feedback.
-
I was wondering if it would be possible to have a 'packages.json' file in embedded C/C++ project which contains the xPacks tools and compiler to install. Then when a user opens the project eclipse could install the tools and make sure paths are correct such that developers have minimal work setting up tools to build new projects.
Thanks
Trampas
Beta Was this translation helpful? Give feedback.
All reactions