Sloeber / arduino-eclipse-plugin

A plugin to make programming the arduino in eclipse easy
https://eclipse.baeyens.it/
420 stars 132 forks source link

MacOS installer incomplete or broken #1682

Open asat232 opened 2 months ago

asat232 commented 2 months ago

macOS Monterey Version 12.6.1 (MacBook Pro Mid 2015) Download link: https://github.com/Sloeber/arduino-eclipse-plugin/releases/download/V4_4_3_0/sloeber-ide-V4.4.3-macosx.cocoa.x86_64.zip After downloading .zip and unzipping, when moving Sloeber.app to application folder having error message "Sloeber.app incomplete or damaged".

  1. Tried to download both Safari and Chrome.
  2. Tried before unzipping move zip from Download folder to another folder in my user root directory.
  3. Used "sudo spctl --master-disable" to have Allow from "Anywhere" in security settings
  4. Tried to install Version 4.4.2 on the same Mac and its installing without issues https://github.com/Sloeber/arduino-eclipse-plugin/releases/download/V4_4_2_0/sloeber-ide-V4.4.2-macosx.cocoa.x86_64.zip
  5. Inspecting content of Sloeber.app (V4.4.3) i see that Eclipse.app is damaged or broken.

So i understand the fast workaround can be to replace Eclipse.app in Sloeber.app If its possible, provide me please with info from where Eclipse.app to take and version of it.

jantje commented 1 month ago

To avoid installation problems you can always compile locally as explained here https://github.com/Sloeber/arduino-eclipse-plugin/blob/master/readme.md

rfbarraza commented 1 week ago

Howdy, seconding this to see if there are any updated for builds?

4.3.2 4.3.3 4.4.3

All seem to have this issue.

jantje commented 1 week ago

As I do not own a mac I do not know nor understand what the problem is.

rfbarraza commented 1 week ago

I do and would be more than happy to help. At least for other macOS folks who find themselves here. :)

From a high-level perspective, it appears that the build process for Macs (at least aarch64 Macs) is not producing a valid build product.

When I attempt to run 4.4.3 I get the following error:

The application cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10827 "kLSNoExecutableErr: The executable is missing" UserInfo={_LSLine=4129, _LSFunction=_LSOpenStuffCallLocal}

Similarly, if I clone the repo and attempt to build locally by running:

mvn clean verify -PSDK,mac64,latest -DskipTests=true && ./build_then_launch.sh

from HEAD of master, I see what seems to be a completely successful build result. But get the following output from build_then_launch.sh:

Searching for the Eclipse executable (with our plugin pre-packaged) to launch
Did not find an Eclipse Arduino IDE executable built.....

Opening build_then_launch.sh, this is because line 3:

file_x86_64="./io.sloeber.product/target/products/io.sloeber.product/linux/gtk/x86_64/Sloeber/sloeber-ide"

is hardcoded for Linux builds. I was able to find the macOS build products in: ./io.sloeber.product/target/products/io.sloeber.product/macosx/cocoa/aarch64

So, while the official build product doesn't seem to be working, you can build it yourself by following the aforementioned instructions.

jantje commented 1 week ago

I do and would be more than happy to help. At least for other macOS folks who find themselves here. :)

That sounds great

mvn clean verify -PSDK,mac64,latest -DskipTests=true && ./build_then_launch.sh

That is not the right command. the -PSDK says you want to build the SDK (that is the eclipse java development environment to help devellop Sloeber) I do not use ./build_then_launch.sh so I can not comment on it working or not.

from HEAD of master, I see what seems to be a completely successful build result. But get the following output from build_then_launch.sh:

As stated above that is because you didn't build io.sloeber.product but build io.sloeber.product.sdk (I know it is confusing)

rfbarraza commented 1 week ago

That is not the right command. the -PSDK says you want to build the SDK (that is the eclipse java development environment to help devellop Sloeber) I do not use ./build_then_launch.sh so I can not comment on it working or not.

Cool, (so assuming the following is correct) running:

mvn clean verify -Pmac64,latest,NOSDK -DskipTests=true

Yields a launch-able build. I can't seem to coerce the v4_4_3_0 tag to build, so I'm comparing HEAD on master to the build products downloaded from the sloeber website. But some quick differences I noticed are:

v4.4.3 is missing:

and has this vestigial directory:

jantje commented 1 week ago

Comparing the current master head to any previous sloeber releases is useless as they are hugely different. I the issue appeared on X compare to x-1. note that you say 4.3.2 fails but @asat232 says it works.