Move Windows build up to latest compilers
Description
Environment
Activity
Rod Widdowson September 8, 2017 at 12:37 PM
1bd109b fixes the component issue which was screwing with upgrades.
I'm declaring victory here, but with https://shibboleth.atlassian.net/browse/SSPCPP-751#icft=SSPCPP-751 and https://shibboleth.atlassian.net/browse/SSPCPP-751#icft=SSPCPP-751 still to do
Rod Widdowson September 7, 2017 at 1:18 PM
I realized over night that the lost DLLS was because of the partial update I'd already done (to VC14 OpenSSL 1.1, so the dll names didn't change but the components did.
I'll wind my VM back to the "VC10 ISAPI" stage before testing any more.
Rod Widdowson September 6, 2017 at 3:26 PM
STATUS:
Built VC15 installer. Appears to be OK for fresh installs (modluo we are not installing IIS7 shib(, but an update drops a whole bunch of DLLs. There will be a component issue somewhere...
IIS7 dll doesn't appear to be working yet either
Rod Widdowson September 5, 2017 at 7:30 AM
If it's not installed shibd won't start. I think that the result is that the install will fail, but it might succedd and shibd not start (starting services is one of those "should be easy but never is" things in the installer.
Detection is of course easy.
99.99%/0.01% solution just look for the damn file in c:\windows\...
I would imaging that while its theoretically possible that it gets installed elsewhere that will never happen (and in particular if you do a tree search you'll find it somewhere)
Corrupt solution : write a free standing plugin (dll) for msi (statically linked, natch) which tries to load the dll and fail if it doesn't. Frankly it would be as much effort to write the damn bundle
I'll do the search for the dll (with a fatal error if it isn't found - that's very easy to code since you don't need to add any new dialogs) as part of this work.
Scott Cantor September 4, 2017 at 5:00 PM
What does it do if it's not installed? I think as long as things are clear, it's fine to just presume it and document how to get it. Even better is if we can fail the install up front without it of course.
Subsequent to #CPPXR-106, #CPPOST-94 we need to move the windows OpenSAML build to use VC14.
Same steps as XML-Tooling & OpenSAML
Create a new projects\vc10 directory (so do many other projects)
Move the build files (sln, vcxproj, vcxproj.filters) into this folder (and children) and pacthing up appropriately
Move the output into build\vc10 (so do many other projects)
Adjust the wxs files to look in this new location
And then derive the VC14 build from the VC10 one