Community
Participate
Working Groups
Build Identifier: I20110613-1736 UniCore32 is a 32-bit RISC CPU designed and developed by Peking University, China. As an answer to the call "One Laptop per Child", our low-cost laptops have been widely used by many students in rural areas in China. Currently we have ported a whole Linux desktop system to UniCore32. Applications such as Open Office and Mozilla Firefox are running well on our laptops. Not long ago, we ported the OpenJDK6. We are eager to se Eclipse running on our laptops. It will be really fantastic for children to do programmings with Eclipse. I downloaded a source of Eclipse 3.7, but found that another native eclipse is needed to compile the source. It seems impossible on our laptops. And I also found there are pre-build SWT libraries for x86 in the source. I'm not familiar with Eclipse's internal. Could you give some instructions to the porting work? Thank you. Cheers, Xingxing Reproducible: Always
The Linux tools project provides an Eclipse build source download that might help. http://wiki.eclipse.org/Linux_Tools_Project/Eclipse_Build You would certainly need to create a new port of SWT to this architecture. Typically native code is built separately and checked into a repository for consumption by the full build.
If you look back in eclipse-build history, you'll see patches for non-x86 arches like Power, m68k, etc. These will be necessary for your architecture, too. http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.eclipse-build.git/ Look in the patches directory ... you may have to look in the history as I don't think they've been ported to 3.7 yet.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
