Jump to content

Antoine Chalons

Members
  • Posts

    955
  • Joined

  • Last visited

  • Days Won

    34

Posts posted by Antoine Chalons

  1. Hi Thomas,

    First, you need to make sure that your dynamically launched VIs are included into the EXE, to do that, in the build specs, in 'Source Files' you have to add these VIs in the "Always Included" list.

     

    Then there path for these VIs will not be the same when you run the code and when you run the EXE

    - in source the VI path is C:\Users\thomas.granito\Desktop\ProjectName\Test.vi

    - in EXE it will be C:\<where-ever-your-EXE-is>\App.exe\Test.vi

    So the easiest will probably be to use a relative path to the main VI.

     

    • Like 1
  2. On 9/13/2021 at 4:59 PM, hooovahh said:

    Okay attached is an updated version that I think supports the changes I made.  It reads the registry in 32 or 64 bit LabVIEW finding the path to the shared installation location.  In Linux it tries both the libeay32.so and libcrypto.so.  In both cases it keeps the found path in a feedback node for later calls.  I also added outputs instead of void for calls, but am now realizing this version doesn't do anything with them yet.

    MD5_my9.vi 32.87 kB · 9 downloads

    why on earth did you use a ring and a property node on that ring to get the method (md4, md5, etc.)?
    an enum with a format into string seems nicer.

    A, also, if your VI used on Linux and built as a shared library (in order to run the app as a service) then it causes a crash.
    With enum+format into string, it works.

  3. I can't get it to work on Ubuntu with LV 2020 SP1

    LabVIEW won't accept the so file and keep asking me to point to the file.

    I've already seen some weird behaviors with CLFN on Linux when feeding the library path on the diagram but if the case of your 64 so file, even if I create a new VI, place a new CLFN and try to link to libmuparser-x64-lv.so LabVIEW then prompts me to find 'libmuparser-x64-lv.so'

     

    image.png.8466b577450cdf89f0d9832083d1a840.png

  4. new release in my fork : https://github.com/AntoineChalons/lv-toml/releases/tag/releases%2Fv2.3.2

     

    what's new : I've improved the error reporting when there is a typo in the value, ex :

    [cluster]
    some-numerial-value = 10
    other-numerial-value-with-a-typo = 10s

    The error source will quote the line at fault and give you the line index, something like "Parsing error at line 3 : 'other-numerical-value-with-a-typo = 10s'

    • Thanks 2
  5. 30 minutes ago, Youssef Menjour said:

    Merci Antoine, it was usefull.

    Glad I could help.
    I don't think the "app store" like model is something NI is willing to invest effort on, they seem happy to let the community deal with it, from what I could see NI did the bare minimum - which is already not too bad - to give the community a reasonably good solution to handle licenses.

    Again I've not used it myself, but I've seen people use, I hope it works out well for you.

    I strongly encourage you to contact NI, and more specifically Nancy Henson or Eric Reffett (look them up on linkedin to see their role at NI) to give them feedback about the developer center on community.ni.com.

    • Like 1
×
×
  • Create New...

Important Information

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