Jump to content

Jim Kring

JKI Team
 View Profile  See their activity

  • Posts

    2,200

  • Joined

  • Last visited

  • Days Won

    105

 Content Type 

Posts posted by Jim Kring

  1. What exactly are VI Package Build Templates (.vipt)?

    in VI Package Manager (VIPM)

    Posted

     

    1 hour ago, LeahEdwards said:

    Am I right in saying they allow you to set the Source Directory, Product Name and Company Name upon opening the .vipt file (including where they are used e.g. in automatic package filename), but pre-set other fields of the new .vipc? 

    Yes, that’s the general idea. Please let me know how it goes.

    BTW, we’re working on updated documentation here (and it’s far from complete) as there are a lot of new features in the works.

    https://docs.vipm.io/package-building/vi-packages-build-templates/

    BTW: the documentation is in a public GitHub repository, so you can suggest edits by clicking on the little edit icon ✍️

    4670DF11-EFB0-43EE-A29B-FD339719036C.jpeg

    -Jim

    • Like 1

  4. General Refactor

    in HTTP REST Client

    Posted

    I agree with your points an am very friendly to this recommendation.

    Would you be willing to collaborate on this effort? It would require writing unit tests, verifying the upgrade process, etc.

    Update: There's a pull request where @jyoung8711 did just this. I think we should take this step foward.

  8. File and Permissions Issues on Ubuntu Linux

    in VIPM Public Beta Discussion Forum

    Posted

    Hi @adamarbor,

    Thanks for giving VIPM 2022 on Linux a try. It's great you've gotten it to start up on Ubuntu (and give some errors) since that can be tricky with alien :)

    First, can you share which build number of VIPM 2022 you're running?

    Next, we've been putting some docs together on ubuntu here: 

    https://docs.vipm.io/linux/ubuntu/

    That doc is far from being super helpful at this point, so I'll share some info here (and we'll be updating those docs along the way).

    A.) Running VIPM as a root user.

    I noticed in your VIPM error log that it couldn't find the LabVIEW config file for the root user (shown below). 

    /root/natinst/.config/LabVIEW-2022/labview.conf

    This means that VIPM was running as root and you have not (nor should you) run LabVIEW as root (which would create/save a LabVIEW config file the root user).

    Tricking VIPM-running-as-root to use your default user's LabVIEW config file

    To run VIPM as "root" and LabVIEW as "adam" you can create symbolic link at "/root/natinst/.config" (where VIPM is looking) that points to the "adam" user's natinst config folder (~adam/natinst/.config).

    Here is an example shell command to create such a link: 

    sudo ln -s ~adam/natinst/.config /root/natinst/.config

    B.) Running VIPM as a normal (non-root) user

    Note that you may not want to run VIPM as root, but rather as your default "adam" user.

    However, running VIPM as a normal user will require you make various VIPM files and folders writeable to normal users.

    Files to Make Writeable to Normal Users (if running VIPM as a normal, non-root user)

    Here are a list of files and folders you will want to make writeable to normal users:

    The VIPM application folder and files: 

    /usr/local/jki/VIPM

    The following folder and files here: 

    /etc/JKI

    The LabVIEW folder and files: 

    /usr/local/natinst/LabVIEW-2022-64

    Also, keep in mind that when VIPM launches LabVIEW, if VIPM is running as root then it'll launch LabVIEW as root.

    You probably don't want to run LabVIEW or VIPM as root.  We're working on a fix that will allow running VIPM as root (e.g via a "sudo" command) but have LabVIEW get launched by VIPM as the user who launched VIPM with the sudo command -- but, that's not implemented yet.

    I hope this is helpful to getting you up and running.

    Let us know how it goes...

  9. Feedback for the Mac beta

    in VIPM Public Beta Discussion Forum

    Posted

    Hi Joerg,

    Quote

    Actually, this "Escape HTTP URL.vi" from vi.lib/wsapi is being used in JKI's REST Client 😉
    For added fun, I found an exact duplicate of the "Escape HTTP URL.vi" inside the JKI REST Client API: "Escape URL String.vi"!

    Yep, this VI exists in several different locations... 🤪
     

    Quote

    I created an issue in the REST Client's GitHub repo: https://github.com/JKISoftware/JKI-HTTP-REST-Client/issues/22 (I'd have loved to create a merge request but I don't have LabVIEW 2013 available, 2016 is the oldest version still in use at HSE).

    Please go ahead and up-save to LV 2016 (or 2017) and submit a PR, if that works OK for you.

    We'll get a new build out.

  11. Feedback for the Mac beta

    in VIPM Public Beta Discussion Forum

    Posted

    Hi Joerg,

    Those notes are great!

    Question: Are you running LabVIEW Professional Edition or the Full Edition on Mac?

    - I'm not sure about vi.lib/wsapi.  It might be a good idea to not rely on that for Escape HTTP URL.vi. If I recall correctly, such a VI has or does exist in several different locations.

    - You may be able to copy vi.lib/Platform/fileVersionInfo.llb over from a Windows machine.

  19. <Tags> in Package Descriptions do not Display on Community Package Page

    in VI Package Manager (VIPM)

    Posted

    Thanks for reporting this issue.

    Right now, the description on the website is taken directly from the package's spec file and the <nothing> string is getting removed because the website has to strip HTML tags from the description.  We're considering good solutions, which might be to just let users manually edit the description on the website (and possibly add a flag that prevents it from auto-updating when new packages are published).

    Regards,

    -Jim

  21. VIPM2020 build for LV15

    in VI Package Manager (VIPM)

    Posted

    Hi @RomainToro,

    Is it correct to assume you do have LabVIEW 2015 installed on your computer?

    Most likely, one of the VIs (or other LabVIEW files) in your package source folder got saved in LabVIEW 2020.  In such cases, VIPM is trying to be "smart" and using LabVIEW 2020 to build the package (but it's not informing you about what it's doing).

    The solution is probably to try opening your source files in LabVIEW 2015 to verify that all of them are saved in 2015.

    Thanks for letting me know.

    -Jim

    • Upvote 1
×
×
  • Create New...

Important Information

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

  I accept