Community
Participate
Working Groups
When I download swt-3.5-gtk-linux-x86.zip I can follow http://www.eclipse.org/swt/eclipse.php and import it into eclipse to create an org.eclipse.swt project that I can develop against. The 3.6 versions no longer contain the .classpath or .project files, and cannot be imported. I downloaded swt-3.6-gtk-linux-x86.zip and swt-3.6-win32-win32-x86.zip from http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/index.php#SWT PW
*** Bug 323601 has been marked as a duplicate of this bug. ***
This change might have been in response to the ability of swt to extract and load its own native libs. But then the doc really needs to be update to tell people what they need to do. PW
SSQ, GG: do you know what could have changed to create this problem ?
Fixed > 20100825. The files were removed between revision 1.6 and 1.7 of buildFragment.xml. There was no good reason to remove them.
(In reply to comment #4) > Fixed > 20100825. > > The files were removed between revision 1.6 and 1.7 of buildFragment.xml. There > was no good reason to remove them. Does this fix apply for both HEAD and R3_6_maintenance?
It is not in 3.6.1 yet. I will see if I can include it for RC3. I do not see any problem, since it does not affect eclipse itself. It only changes the SWT standalone zip.
Created attachment 177428 [details] patch for 3.6.1
Created attachment 177435 [details] patch for 3.6.1 The previous patch was generated wrong.
The patch has been released to R3_6_maintenance and the SWT projects have been tagged. So we are ready if there is a rebuild for RC2, otherwise I will ask for PMC approval for RC3.
(In reply to comment #9) > The patch has been released to R3_6_maintenance and the SWT projects have been > tagged. Thank you very much, Silenio.
> I will ask for PMC approval for RC3. +1 for RC2 or RC3.
*** Bug 310826 has been marked as a duplicate of this bug. ***