Community
Participate
Working Groups
This bug is to investigate/upgrade SWT to latest VisualStudio and Windows-SDK.
Started experimenting SWT with below on a Windows10 machine: 1. Latest Windows 10 SDK 2. VisualStudio 2017 community edition
(In reply to Niraj Modi from comment #1) > Started experimenting SWT with below on a Windows10 machine: > 1. Latest Windows 10 SDK > 2. VisualStudio 2017 community edition I am using the "VisualStudio 2017 Community Edition" which is free, corresponding web installer link for reference: https://www.visualstudio.com/thank-you-downloading-visual-studio/?sku=Community&rel=15
New Gerrit change created: https://git.eclipse.org/r/111780
(In reply to Eclipse Genie from comment #3) > New Gerrit change created: https://git.eclipse.org/r/111780 Above is a working patch.. have workaround few unknowns, which still needs to be analyzed.
(In reply to Niraj Modi from comment #4) > (In reply to Eclipse Genie from comment #3) > > New Gerrit change created: https://git.eclipse.org/r/111780 > > Above is a working patch.. have workaround few unknowns, which still needs > to be analyzed. Addressed the workarounds, latest gerrit patch is ready to go. Waiting for the bug 528319 to be addressed.
Hi Conrad, If possible, can you try the latest gerrit patch on you local setup ? You will need to install latest Windows 10 SDK and VisualStudio 2017 community edition SDK which are free, for exact details you can refer below: https://bugs.eclipse.org/bugs/show_bug.cgi?id=528319#c0
Gerrit change https://git.eclipse.org/r/111780 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=c5e9c5f34ab0f7d4b11000197dda66a4d6564911
(In reply to Eclipse Genie from comment #7) > Gerrit change https://git.eclipse.org/r/111780 was merged to [master]. > Commit: > http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/ > ?id=c5e9c5f34ab0f7d4b11000197dda66a4d6564911 With above changes, we have are done with the necessary changes in SWT build scripts/code to move to the latest Windows 10 SDK and Visual Studio 2017 SDK. Also done with the SWT native build input, all seems fine. Tonight's Eclipse Windows build will be consuming the latest binaries.
(In reply to Niraj Modi from comment #8) > (In reply to Eclipse Genie from comment #7) > > Gerrit change https://git.eclipse.org/r/111780 was merged to [master]. > > Commit: > > http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/ > > ?id=c5e9c5f34ab0f7d4b11000197dda66a4d6564911 > > With above changes, we have are done with the necessary changes in SWT build > scripts/code to move to the latest Windows 10 SDK and Visual Studio 2017 SDK. > Also done with the SWT native build input, all seems fine. > > Tonight's Eclipse Windows build will be consuming the latest binaries. I20180105-2000 and on-wards Eclipse Windows builds are consuming the binaries built using the latest Win10SDK and VS2017. Will be refactoring the build.bat to work with updated directory structure on the Eclipse Foundation build machine.
New Gerrit change created: https://git.eclipse.org/r/115058
Gerrit change https://git.eclipse.org/r/115058 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=93e4378c824ab449f9ae4b4fc4fe7c9e0f13e776
(In reply to Eclipse Genie from comment #11) > Gerrit change https://git.eclipse.org/r/115058 was merged to [master]. > Commit: > http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/ > ?id=93e4378c824ab449f9ae4b4fc4fe7c9e0f13e776 Above patch does the required clean-up of the build.bat and now matches the directory structure of current Windows build machine on Eclipse Foundation. In our testing we haven't noticed any major changes w.r.t. Eclipse UI or SWT widgets, waiting for community feedback.
SWT Windows native setup page has been updated for newer SDKs: https://www.eclipse.org/swt/swt_win_native.php Resolving this bug now.
Verified latest Eclipse 64/32bit Builds Id: I20180122-2000 on Win7/Win10.
*** Bug 544750 has been marked as a duplicate of this bug. ***
*** Bug 541523 has been marked as a duplicate of this bug. ***