- Microsoft visual studio 2017 community edition update#
- Microsoft visual studio 2017 community edition windows 10#
- Microsoft visual studio 2017 community edition code#
The newest version of Microsoft's 20-year-old Visual Studio product allows developers to grab only the specific components they need, making its installation faster.
Microsoft visual studio 2017 community edition windows 10#
Microsoft's latest tool suite will run on Windows 10 (version 1507 or higher) Windows 7 Service Pack 1 Windows 8.1 Windows Server 2016 Standard and Datacenter Windows Server 2012 R2 Essentials Standard and Datacenter. They may want different things but ultimately the dynamic between CIOs and developers can be highly beneficial for the businesses that employ them. NB: If debugging NPP from within VS, enable Multi-instance in NPP settings or close other instances of notepad++.Why CIOs and developers are seldom on the same page - and why that's a good thing Open \notepad-plus-plus-7.8.2\PowerEditor\\notepadPlus.vcxproj in VS2017.To \notepad-plus-plus-7.8.2\PowerEditor\\Unicode Debug\ Copy \notepad-plus-plus-7.8.2\scintilla\bin\SciLexer.dll.nmake BOOSTPATH=\boost_1_72_0\ BOOSTREGEXLIBPATH=\boost.tmp\ -f scintilla.mak.NB: Contrary to github guide (step 4), I found libboost_regex-vc141-mt-s-x32-1_72.lib in: \boost_1_70_2\b2.exe toolset=msvc link=static threading=multi runtime-link=static release stage.Open “Visual Studio 2017 Developer Command Prompt”.It worked pretty smoothly, except for minor difference with boost_1_72_0 compared to boost_1_70_0. Changed the VS “Solution Platform” from 圆4 to x86īuild notes for NPP v7.8.2 32bit with Visual Studio 2017 on Win10īuild process on NPP’s github has been updated to no longer include requirement for BuildBoost*.bat.When opening notepad-plus-plus-7.6.3\PowerEditor\\notepadPlus.vcxproj the first time, I was prompted by VS to “Retarget Projects” to v141_xp.Copied scintilla\bin\SciLexer.dll to PowerEditor\\Unicode Debug\.So I just continued using Boost 1_65_1 (and Gary Bloom’s above buildboost2017.bat). This can be worked around using -toolset msvc-14.1, but then scintilla.mak fails with some architecture related error from Boost source…īoost_1_69_0\boost/type_traits/detail/is_function_cxx_11.hpp(111): error C2218: '_vectorcall' cannot be used with '/arch:IA32' This causes issue in BuildBoost.bat since it can’t autodetect the library file. Since Boost 1_66_0, the Boost lib file name structure now has extra “x32” detail: NB: There is a certificate check for SciLexer.dll that will fail with newly built version… so I commented out call to VerifySignedLibrary in loadSciLexerDll() function as kindly suggested by dail here… įirst looked at using latest Boost 1_69_0, but failed. Now should be able to open ‘C:\Source\notepad-plus-plus-master\PowerEditor\ \’ and proceed. (boothpath.mak should now have been created containing path to Boost source and also to newly generated Boost regex libs)Ĭd C:\Source\notepad-plus-plus-master\scintilla\win32 Launch BuildBoost: (NB: BuildBoost-VS2015edit.bat requires -toolset parameter after path to boost!) Launch ‘Developer Command Prompt for VS2015’ from Start MenuĬd C:\Source\notepad-plus-plus-master\scintilla\boostregex
Microsoft visual studio 2017 community edition code#
NB: BuildBoost.bat does not support -toolset since PARAMLOOP code is commented out, so hacked version requires this parameter order:īuildBoost-VS2015edit.bat PathToBoost īuildBoost-VS2015edit.bat C:\Source\boost_1_63_0 -toolset msvc-14.0
‘BuildBoost-VS2015edit.bat’ also adds case for msvc-14.0 target path since it’s required to auto-generate the scintilla make file. (NB: b2.exe is exact same as bjam.exe! See - )īoost 1_63_0 has bootstrap.bat & b2.exe in ‘…tools\build’ instead of ‘…tools\build\v2’ so minor edit of npp’s BuildBoost.bat required, so created ‘BuildBoost-VS2015edit.bat’ in same folder. (Older boost versions may need to have visualc.hpp edited as described here - ) Using current boost version 1_63_0 which natively supports VS2015.
Microsoft visual studio 2017 community edition update#
Using Microsoft Visual Studio Community 2015 Version 1.01 Update 3 (most options installed)
Ĭ++ and all this linking malarky isn’t my usual poison so I can’t offer expert advice, but I took notes as I went and I’ve uploaded the modified BuildBoost.bat here…
I just managed to get it working with boost 1_63_0 / VS 2015 / msvc-14.0.