- This topic has 9 replies, 6 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
The Eclipse group finally released a Univeral Binary that runs on the Mac Intels. The release is 3.2M5. Do you guys have any plans to migrate your development releases to version 3.2 of Eclipse?
-J
J,
The univ binaries only effects native code AFAIK, so we don’t need to change anything for MyEclipse for it to run on the Mactels. So if the question then becomes “when is your 3.2 compliant version comming out”, I’ll say that it will be version 5.0, and we will release our first milestone around EclipseCon and then try and have a final release by the end of June/July.@support-rkalla wrote:
J,
The univ binaries only effects native code AFAIK, so we don’t need to change anything for MyEclipse for it to run on the Mactels. So if the question then becomes “when is your 3.2 compliant version comming out”, I’ll say that it will be version 5.0, and we will release our first milestone around EclipseCon and then try and have a final release by the end of June/July.Yeah, I realized that there wasn’t a dependency per se between the Universal Binaries for Eclipse and MyEclipseIDE, but without a version of Eclipse that runs on the Mac Intel, MyEclipseIDE is not an option. I’m using NetBeans 5.0 (actually pretty nice) until I can download a version of MyEclipseIDE that runs on Eclipse 3.2.
Are there any known issues for trying to run MyEclipse 4.1.1 on top of Eclipse 3.2M5? Has anybody tried it?
tia,
./alex
—
.w( the_mindstorm )p.Alex,
It simply will have several problems, some of which might impact you and some that don’t. Basically, 3.2 changed several APIs and introduced compilation errors in our current code base as a result. So, stuff is *definately* broken at this point with a 4.x / 3.2M combination.
So when is this likely to be?
@support-rkalla wrote:
We’ll try and get our first 5.0 milestone out shortly, sorry for the delay.
@jcorbin4607 wrote:
@support-rkalla wrote:
J,
The univ binaries only effects native code AFAIK, so we don’t need to change anything for MyEclipse for it to run on the Mactels. So if the question then becomes “when is your 3.2 compliant version comming out”, I’ll say that it will be version 5.0, and we will release our first milestone around EclipseCon and then try and have a final release by the end of June/July.Yeah, I realized that there wasn’t a dependency per se between the Universal Binaries for Eclipse and MyEclipseIDE, but without a version of Eclipse that runs on the Mac Intel, MyEclipseIDE is not an option. I’m using NetBeans 5.0 (actually pretty nice) until I can download a version of MyEclipseIDE that runs on Eclipse 3.2.
Actually, you can easily run a universal binary version of Eclipse 3.1.x as well – I’m doing so. There a simple patch script that recompiles the SWT native code for Intel and that’s all you need, the rest of Eclipse is pure Java.
Sorry – forgot to provide a link to the patch: http://forum.osx86project.org/index.php?showtopic=4601&hl=eclipse The said patch runs against 3.1.1, but it is the same procedure for 3.1.2 – just open the patch file in textedit or something similar and modify the paths as necessary.
