As a user I want to be sure pytrnsys runs TRNSYS with the DLLs released with pytrnsys. Hence pytrnsys should at startup always check that
If there is a DLL foo.dll in the TRNSYS DLL folder which exports a function (e.g. func7) of the same name as a function exported by a Dll x in the pytrnsys folder, then x = foo.dll and the hashes of both foo.dlls must be the same (i.e. they must [almost certainly ;)] be binary equal)
All the DLLs in the pytrnsys DLL folder should also be in the TRNSYS DLL folder (looking at the names). If this is not the case tell the user to run the copy-dll script and re-run pytrnsys
There should be no collisions of exported functions across all TRNSYS DLLs.
pytrnsys should refuse to run unless all of the above conditions are satisfied (possibly we can add a command line argument to override this behavior).
zuckerruebe
commented
2 years ago
As a user I want to be sure
pytrnsysruns TRNSYS with the DLLs released withpytrnsys. Hencepytrnsysshould at startup always check thatfoo.dllin the TRNSYS DLL folder which exports a function (e.g.func7) of the same name as a function exported by a Dllxin the pytrnsys folder, thenx=foo.dlland the hashes of bothfoo.dlls must be the same (i.e. they must [almost certainly ;)] be binary equal)pytrnsysDLL folder should also be in the TRNSYS DLL folder (looking at the names). If this is not the case tell the user to run thecopy-dllscript and re-runpytrnsyspytrnsysshould refuse to run unless all of the above conditions are satisfied (possibly we can add a command line argument to override this behavior).