28 Oct
2019
28 Oct
'19
9:59 a.m.
On 28.10.19 00:08, pat pagano wrote:
I also noted that one must load iemlb now as well at startup not just it's path
this has *always* been the behaviour if iemlib.
some people thought it nicer to only need to specify the path, and distributed binaries that did not require to load the "iemlib" libraries. but this was always done without the consent of the upstream author (tmusil), and now that the people who provided those binaries stopped doing so you only get upstream's preferred format.
the good news is, that there's no longer a(n arbitrary) distinction between "iemlib1" and "iemlib3" and ... and you simply have to load "iemlib" and add it's path. preferably via [declare -path iemlib -lib iemlib] instead of startup options.
gfdmsft IOhannes