Jump to content

Olivier Jourdan

  • Content Count

  • Joined

  • Last visited

  • Days Won


Olivier Jourdan last won the day on July 10

Olivier Jourdan had the most liked content!

Community Reputation

3 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For information, I recreate the vipb from scratch, and I still have this error 🙁
  2. 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.
  3. Hi @Jim Kring, any updates on my issue ? Thanks in advance.
  4. Hi Jim, You can simply fork this project https://gitlab.com/wovalab/open-source/asciidoc-toolkit and try to build the vipb you'll find at the root of it. Thanks in advance for your feedback.
  5. Hi Jim, That was the setting I knew that exists and didn't find last night (I was probably too tired 😇). Anyway, I gave it a try this morning without success. I got no error, but text wasn't appended to vi description. Any idea ?
  6. Hi everyone, I'd like to change the description of the VIs contained in my package during the build process (to add BSD licence text). I created a pre build action and used the path array to add description to VI. It seems that the action vi is not called. What am I doing wrong ? Thank in advance for any help. Note: I'm using VIMP 2020 community edition
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.