Quote:
Originally Posted by DiapDealer
Not really sure, to be honest. My gut says no (no there shouldn't be any issues), but Windows is so weird about how memory-resident functions of dlls work/persist, that I wouldn't swear to it. The sigil-specific dlls (python35 gumbo and hunspell) shouldn't cause any issues. Because 1) they've not been altered between 0.9.9 and 0.9.10; 2) they were all built with VS2015; and 3) Windows first priority for library search paths is the current directory (so all of those libraries are packaged adjacent to the Sigil executable for that exact purpose). The environment for the python-based plugins (run in a separately executed process) is tightly-controlled and should pose no problems.
Just remember they'll share the same preferences unless you launch one version of Sigil with the SIGIL_PREFS_DIR set to somewhere else.
|
I'll summon up the courage to give it a go, I'll let you know the results.
Your discussion with Ruben has echoes of the problems I had with Sigil and the C++ libraries in the distant past - which is what prompted my question.
At the time I had dozens of "Microsoft Visual C++ 2008 Redistributable - XXXXXXXX" installed, I'm now down to a mere eight - only one of which is 2015. Not sure what I did, or more probably what MS did, to reduce the number, that happened when I was still using Win7.
BR