Error when searching dependency in former location during package building process

[Wovalab]

Hi JKI Team,

I'm facing an issue building a package since I've changed the dependent package's destination path.

For the record, this impacts Antidoc open source project

Let me explain.

Antidoc package (called A) relies on the Asciidoc Toolkit package (called B).

Library of B was formerly installed in ../B/Sources/B.lvlib. I modified the vipb to have the library installed in ../B/B.lvlib

I made the same modification for A. As it worked fine for B, I now have an error for A. VIPM is expecting to find some VIs in ../B/Sources folder that not exists anymore.

I checked that A code didn't keep any older links, but I still have the error.

 

The only workaround I found to be able to build the package is to duplicate the content of the B folder in a ../B/Sources folder. This way, A code finds its dependency, and VIPM doesn't throw an error. 

 

Installing B (no duplicated Sources folder) and A works fine.

 

I can't see where I did something wrong in the process. Did someone already come across this error? Any idea to fix that and avoid it in the future?

 

Thanks in advance for any idea or help. Feel free to clone the Antidoc repository to reproduce the issue.

[Wovalab]

For information, I recreate the vipb from scratch, and I still have this error 🙁

[Wovalab]

A quick update on that issue.

I eventually fixed it! For that I create a blank project and dropped lvlib contained in my working project. Here is the "magic", LabVIEW started to throw me dialog box to find VIs it couldn't find at an old expected place (almost the same error reported by VIPM). After resolving these conflicts, the package is building fine.

The really strange thing is that conflicts never shown in the working project...

Hope this can help.