Jump to content

Zaphiro Technologies

Members
  • Posts

    25
  • Joined

  • Last visited

  • Days Won

    1

Zaphiro Technologies last won the day on February 13

Zaphiro Technologies had the most liked content!

About Zaphiro Technologies

  • Birthday 09/10/1981

Contact Methods

  • Website URL
    https://www.linkedin.com/in/antoinechalons/

Profile Information

  • Gender
    Male
  • Location
    Lausanne

Recent Profile Visitors

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

Zaphiro Technologies's Achievements

Enthusiast

Enthusiast (6/14)

  • Reacting Well Rare
  • One Year In
  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

14

Reputation

  1. in 4.2.1b1 the lib path was '/usr/local/natinst/LabVIEW-2020-64/user.lib/_OpenG.lib/lvzip/lvzlib.*' for all CLFNs also another issue, that I also see on Windows as well as Linux is that the LVZip sub-palette is not showing up in the OpenG palette
  2. i manually extracted the lvzlib64.so from the ogp and replaced it in /user.lib/_OpenG/lvzip and renamed it to lvzlib.so then re-selected it in all the clfns then it works...
  3. after re-writing the post-install VI in this way I could get the package to install but then I have other issue with the clfn : dll on Linux doesn't go down too well and when I try to select the lvzlib.so, LabVIEW complains that
  4. I can't install this package on Linux (even after uninstalling the previous version, 4.2.1b1) I keep getting an error during the post-install : I'm using VIPM 2017 and on Ubuntu I have to run it as root to make it work, I suspect that could the the issue.
  5. i enable the "Do Not Compile on Build" option (in Source file settings section) and the package building worked and took a lot less time than before. As I mass compile my source folder anyway before building the package, am I risking anything? Why is this option "not recommended"
  6. side note : I'm still able to build other (smaller) packages successfully
  7. I get this error when building my package, previously the package was building fine, it did taka a long time (~15 to 20 minutes) to build though because it's quite large (~78 classes, 1200+ VIs). Since the last successful build I've only added some methods in the classes. Sources are in LV 2019 32 bit I'm using the latest version of VIPM 2021.1 b2754
  8. I "repaired" LabVIEW 2019 using NIPM Rebooted Uninstalled VIPM, re-install (runnning the install as admin of course) Rebooted now it seems to work again
  9. I've just installed the LV 2019 SP1 patch (f5) from NIPM and now won't launch. The splash screen comes up, then disappears. After that in the task manager I still have VIPM in the back-ground services : Anyone having the same issue?
  10. this solution worked for me on Ubuntu 20 : https://lavag.org/topic/21815-installing-vipm-1702018-linux/?do=findComment&comment=137641
  11. I've checked, my package does not depend on any other package. There was an vipc file (1kb), I deleted it, forced VIPM 2021 (2745) to check again for dependencies (still none) no *.vipc file created next to my *.vipb file package creation still fails.
  12. sorry, right after posting this I went to check if this issue had already been reported... it seems it has :
  13. I have package (LV source in 2019 SP1 32 bit) that builds just fine when I use VIPM 2020.3 But VIPM 2021 beta (2745) keeps failing with this message : In both cases VIPM Pro license was activated. Any idea what could cause this?
×
×
  • Create New...

Important Information

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