[CURA-12675] workaround for anti-virus forcing version of DLL on Cura #164
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sion of MSVCP140.dll instead of ours. See actions/runner-images#10004 (comment) -- and that thread in general. Which is the same as an issue we _originally_ tried to work around by going with an older MSVC (which is what Lulzbot ended up going with) and when that turned out to not work, we just upgraded the entire chain to the new version. -- _However_ it now apprears that an antivirus vendor (McAfee) is forcing their own version of those DLL's, which are the older ones. -- So now try this workaround. CURA-12675
If this ends up not working either, we should propbably rely on the (same) alteration in the generate step instead. CURA-12675
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The dynamic lib
MSVCP140.dll(and related) comes in two distinct flavours -- one pre-fix and one post-fix -- according to MS this technically doesn't break compatibility and is 'By Design'. (But it's not really them that are to blame in this particular case.)In any case, this was a bit of a problem for us -- but one we thought to have (eventually, after some detours) solved with the workaround of just building everything with the newer version and then forcing the newer ones to be high up in our
PATH.Que certain anti-virus vendors (McAfee) just straight up forcing programs to use certain DLL's -- which is a can of worms just in and of itself, and from the above context you can begin to guess which particular worm bit us in this case.
Yes, that's right, they're forcing us to use the old version of
MSVCP140.dll.Fortunately, MS was at least graceful enough to have 'an escape hatch' as they put it, so that's what we're using here. Even though we actually shouldn't need it, since we where using the newer version (originally).
Anyway we should be good now, whatever version of that DLL anyone has.