Closed thomasliebenau closed 7 years ago
Thanks Thomas. I'll fix that this morning. I should test installation on a separate virtual machine ;-)
Well, I think something is corrupted in the linker info of one of the classes, which causes VIPM to believe that the classes associated with the Facade class are in the wrong location. The duplicate does not make sense otherwise. I thought I had a cross-link somewhere, or a circular dependency, but that's not it. It will take a bit more work to get that right.
In the meantime, I think the code still works after relinking as the classes are really duplicates, but people should wait for the next build before trying it out.
So, the culprit is that one of my dependencies had been moved into the test folder, which was not supposed to get built into the package. By pulling this dependency into the package, the file was put at the root and it duplicated the classes it depended on... causing a linkage issue.
Hi,
package 1.2 installs with conflicts in dependencies:
Many (all?) lvclass files are duplicated to the package base folder and VIs are relinked to them except regestry-smo.lvclass which raises a dependency conflict.
With package 1.1.17 folder looked like that:
with best regards, Thomas Liebenau