Thank you very much, Sravan. Before trying to compile, we had this crazy idea that worked.
At the same time we're maintaining our Eclipse 3-based application, which needed a solution to the menus problem I mentioned in the first email, we're porting it to be Eclipse 4-based. As the menus problem does not happen on the Eclipse 4 port, and as we had already pin-pointed that the problem is the executable file, we came up with the idea of using the executable of the Eclipse 4-based on the Eclipse 3-based and voilà! Problem solved. We can ship the Eclipse 3-based app using the Eclipse 4-based executable. Sounds like pure WOP - Workaround Oriented Programming? For sure! 😋 But it won't be like this for long, because our Eclipse 4-based is coming soon. So we're fine. Thanks again, Sravan. And thanks to Lars, too. Mario Marinato ~ Rio de Janeiro/Brazil Em ter., 10 de out. de 2023 às 09:19, SRAVAN LAKKIMSETTI < sravankum...@in.ibm.com> escreveu: > Building native launcher is straight forward. The code is in > https://github.com/eclipse-equinox/equinox/tree/master/features/org.eclipse.equinox.executable.feature/library. > Switch to cocoa folder and run build.sh. it will build the launcer > executable and its companion .so file. Replace them in your existing > installation. > > > > Prerequisites for this would be latest Xcode with macos SDK to be > installed. > > > > I hope this helps. > > > > Thanks > > Sravan > > > > *From:* platform-dev <platform-dev-boun...@eclipse.org> *On Behalf Of *Mário > Marinato via platform-dev > *Sent:* Monday, October 9, 2023 4:29 PM > *To:* Eclipse platform general developers list. <platform-dev@eclipse.org> > *Cc:* Mário Marinato <mariomarin...@gmail.com> > *Subject:* [EXTERNAL] [platform-dev] Recompiling Mac's native launcher > > > > Hello. I'm part of a team that develops an RCP application that is still > based on the Eclipse 3 framework. I know we should've migrated years ago, > we're porting it now, but the current version of our system is still alive > and needs > > ZjQcmQRYFpfptBannerStart > > *This Message Is From an External Sender * > > This message came from outside your organization. > > * Report Suspicious * > <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!12-vrJDXKdXVsIUQlE8vB-9SnX8flMLD3DNACwIkU70mpm-C3lu2uiKByZxTPrpJGqelNhlly6ApPzBvDsCg0tOwPzt4Zedq5uza8Q3iY_5GTTgHsj_NRAggjW_Tbg$> > > > > ZjQcmQRYFpfptBannerEnd > > Hello. > > > > I'm part of a team that develops an RCP application that is still based on > the Eclipse 3 framework. > > > > I know we should've migrated years ago, we're porting it now, but the > current version of our system is still alive and needs maintenance, and > that's why I'm here. > > > > The recent release of the new MacOS, Sonoma, broke our menus (see here > <https://stackoverflow.com/q/77229905/431>), and we discovered that the > source of the problem is the native launcher. If we launch our application > using java -jar plugins/org.eclipse.equinox.launcher.jar, the menus work > as expected. > > > > We then started building an executable jar that performs the call and > handles all the other tasks needed (reading the .ini file, handling > restarts, so on). > > > > But then this idea came to me, that recompiling the native launcher might > solve the problem. This way, we would not need to mess around with a > different executable jar. > > > > Do you think this is possible? If so, is there a page with detailed > information on how we could achieve this? > > > > Thanks. > > > > Mario Marinato > ~ Rio de Janeiro/Brazil >
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
