I've reverted back to a system restore point prior to when I installed the Visual Studio 2010 stuff plus the problematic Windows SDK. That fixed my problem with right-clicking crashing Windows Explorer. Oh and yes, prior to reverting back to an earlier safe point, had I already tried to use ShellExView to disable possible problematic Context Menu entries on the right-click menu, which is usually the cause for the crashes. That didn't help me out.
This does mean that my system is now rid of the Visual Studio installation and the SDK. And I am not going to install it again to then possibly break my system again. So, next thing for me to do is install Windows in a VM, update it, then add Visual Studio and the SDK to that installation, to then continue my writings. Unless there's a quick-route for this I haven't noticed yet. -- Jord van der Elst. On Thu, May 22, 2014 at 6:14 PM, Jord van der Elst <els...@gmail.com> wrote: > Okay, > > So the old CompileClient page is really out of date by now. Do we want > a new one, or is it better that Windows users use as much as possible > the official recommended version, and that those that like to live > dangerously can use an exotic like a development version? > If we want a new CompileClient page for Windows, I don't mind writing > it. I'll just need pointers, such as what are the requirements these > days, which version of VS2010 at minimum, which service pack, which > SDK? > Do we need pre-built OpenSSL, Zlib, LibCurl, SQLite3, and other > libraries, or are they only in self-built versions available? > WxWidgets is 3.0, but what else? > > Rom and I wrote the original CC page for Windows, and I know it was > broken within months of us putting in the final dot, so I assume > that's going to be the case now as well. > Perhaps it is better that Windows users use the Berkeley built versions... :-) > > -- Jord van der Elst. > > > On Thu, May 22, 2014 at 6:00 PM, Rom Walton <r...@romwnet.org> wrote: >> Over the last few months I've been pruning the source tree of legacy Windows >> code. 1200+ lines so far. >> >> >> >> I suspect that BOINC will not even compile on VS 2005 anymore. I removed a >> bunch of #defines from hostinfo_win.cpp which are present in the VS 2010 >> Windows SDK but not in the VS 2005 Windows SDK. There were also a bunch of >> places where we were doing a LoadLibrary/GetProcAddress instead of calling >> the API directly so that we could run on older versions of Windows. I've >> been cleaning that up as well. >> >> >> >> The commit in question just modified a shell script used by one of VS's >> post-build events to update DLLs in the build directory. I also use the >> same script to validate/upload symbol files and code sign the stuff we >> release. >> >> >> >> ----- Rom >> >> >> >> From: korp...@gmail.com [mailto:korp...@gmail.com] On Behalf Of Eric J >> Korpela >> >> >> Sent: Thursday, May 22, 2014 11:19 AM >> To: Jord van der Elst >> Cc: Rom Walton; BOINC Dev Mailing List >> Subject: Re: [boinc_dev] WINBUILD: Minimum supported VS is now VS 2010 >> >> >> >> Nothing quite like spending a few hundred dollars to compile free software, >> is there? It's not clear from Rom's message whether the incompatibility is >> in the project files (or that it's too much work to maintain the old project >> files), or whether its a newer visual C++ version that is necessary. If >> it's just the maintenence of old project files and required libraries, a >> volunteer could do it. >> >> As a means of relaxing, I've been slowly working on cross compiling with >> mingw32/64 on Linux and Cygwin, but, of course, there's no clear indications >> of what features are necessary in wxWidgets to compile boincmgr. At least I >> have the libraries and client compiling. Of course, MSVC++ happily and >> silently compiles things that aren't legal on gcc (like implicit conversions >> from string to char *, what's that about?), so there are a hunderd things to >> fix to get it working. >> >> >> >> On Thu, May 22, 2014 at 7:54 AM, Jord van der Elst <els...@gmail.com> wrote: >> >> WINBUILD: Minimum supported VS is now VS 2010 >> >> So then that means that someone has to retest and rewrite all and everything >> of >> http://boinc.berkeley.edu/trac/wiki/CompileClient#Windows as the >> compilers the page is written for are VS 2005 (Express) and 2008. >> >> And what VS, full VS or is Express also an option? >> Or is Express still not capable of compiling 64bit applications? >> >> Thanks, >> >> -- Jord van der Elst. >> _______________________________________________ >> boinc_dev mailing list >> boinc_dev@ssl.berkeley.edu >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. >> >> _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
