Community
Participate
Working Groups
It seems that the source archives are missing the ppc64 swt fragment. When I build on ppc64, I get this error: /eclipse-3.2.0/build.xml:71: /eclipse-3.2.0/plugins/org.eclipse.rcp.source.linux.gtk.ppc64/src not found. I think that the missing swt fragment is causing this. Would be be able to get this fixed for 3.2? Thanks, Ben
The swt fragment is missing. This will not be fixed for 3.2 because it is not an official reference platform in our project plan and 3.2 is essentially shutdown. http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html#TargetOperatingEnvironments Are you interested in contributing this fragment for 3.3? I don't think we have the hardware here to support this port. http://www.eclipse.org/eclipse/platform-releng/contributingEclipsePorts.html
We seem to be moving away from using proprietary JREs so I don't think I could commit to providing builds for ppc64. IMHO I think the best way to move forward with platform coverage is to improve the build process. It would be nice to be able to easily build Eclipse on non-reference platforms. You guys could still provide the builds for the platforms you think are important, but there would be mechanisms in place to build Eclipse on the stranger platforms. I think that there's a good argument here because there will always be more platforms than you can provide builds for. For example, we're interested in integrating Eclipse into the s390 and s390x platforms and I doubt there is interest for this from the broader Eclipse community. I thought about how we could improve the build for stranger platforms and I think there are two things that need to be fixed to make building easier: (1) give eclipse the ability to build itself without an installed eclipse or without pre-generated build.xml files (i.e. figure out a way to let pde.build bootstrap itself so it can generate the build.xml files at build time) and (2) autotool all the native code including SWT (we could use cygwin on for compiling on windows *if* ppl want to compile the native libs - there should still be the option of using the pre-compiled libs). Once these two things are done, I think it would be possible generate the fragments at build time base on the properties of the platform and/or arch. Anyway, just some random thoughts.
Ben, I understand your issues with our build process. We are certainly open to improvements in it. We also welcome contributions from other teams building eclipse. For instance, today Sun contributes solaris-gkt-x86, and Intel contributues win64-x86, win64-ia64, and linux-gtk-ia64. We are happy to let other people build platforms because we don't have to buy every combination of hardware for our lab, and they are responsible for solving platform specific bugs. We also welcome contributions from people who would like to build against other VMs other than the ones we use in our build process. Regarding your suggestions 1) Bootstrapping PDE Build - If you are asking for pde build to be bootstrapped, are you also suggesting that it's 17 plugin dependancies be also bootstrapped? The build.xml for each plugin and features are generated at build time, unless they have a custom build.xml. We just copy the files over to be included in the source build. 2) I'm not sure what you mean by autotool all the swt code. Could you explain in more detail. There is the option to recompile the swt libraries from source using the -compilelibs flag during the source build.
Regarding comment #2 point 2, I talked to Grant and Steve from Steve Billy wanted to do this (if I understand right). Nobody here has the time to invest in it (although it is important for open source distriobutions). Is there an existing bug open against swt to implement their build scripts using autotools? Is this the one you were talking about? https://bugs.eclipse.org/bugs/show_bug.cgi?id=71636 If so, we can add a helpwanted tag to it.
(In reply to comment #4) > Is there an existing bug open against swt to implement their build scripts > using autotools? Is this the one you were talking about? > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=71636 No I was actually thinking of bug # 71637, but this one seems more appropriate. > If so, we can add a helpwanted tag to it. Yeah, that would be good. You should also change the summary to make it clear that the helpwanted flag refers to a request to autotool SWT.
*** This bug has been marked as a duplicate of bug 71636 ***
