-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails for Linux aarch64 and on macOS with Apple silicon chip #182
Comments
A summary describing what happened when I tried to build Capella Studio 6.0.0Information about the Fedora container I use:
When I download and extract the source code from the release https://github.com/eclipse/capella-studio/releases/tag/v6.0.0 and run the command I get the errors:
So in summary the most important StdErr output is:
|
Hi Jamil, Capella-Studio is currently built (master branch) in a Jenkins CI on https://ci.eclipse.org/capella/job/Capella-studio/job/master/ You current error comes from the not existing .target file. You can take a look at the Generate Target Platform step of the Jenkinsfile. Pay attention that the tagged commit corresponds to the commit done just before the release, the location urls in the capellastudio.targetplatform still refer some "stable" url which might have been removed since then or "master" references which now corresponds to the 7.0.0 version. If you want to build a 6.0 version, you will have to rewrite the target platform definition with locations corresponding to "v6.0.0" (including the main included Capella target platform) Then if you want to build a product for aarch64 environments, If you want to build a product for aarch64 environments, you will have to modify at least:
Regards Note: I have put the link towards the v6.0.0 tag. |
Hi!
It would be of great help to have a download for a Capella Studio release which is built for Linux aarch64.
I could not get it to build and need to be able to develop a Capella extension for Capella 6.0.0.
Many thanks,
Jamil
The text was updated successfully, but these errors were encountered: