Jump to content

Recommended Posts

I have installed Labview 2020 on Dedian Buster using the rpm to deb conversion method via alien. Due to Architecture mismatch i deleted the *i386.rpm files before conversion.

My Problem is that after creating a project at "Build Specification"-> "rigth click" i am only able to select "Source Distribution". Application does not show up as an option. 

I will be grateful for any suggestions.

Thank you in advance.

Link to post
Share on other sites
2 hours ago, Yaw Mensah said:

My Problem is that after creating a project at "Build Specification"-> "rigth click" i am only able to select "Source Distribution". Application does not show up as an option.

Which edition of LabVIEW did you install?

The Application Builder comes with LabVIEW Professional. It is not included with LabVIEW Base or LabVIEW Full.

Link to post
Share on other sites

It is a LabView Professeional. The Iso contained an Insataller for Mac and Linux.  The installation on a Mac went good and the option "Application" was available. But on Linux, Debian Buster, the option is not available.

Link to post
Share on other sites

I can build executables on my installations of 2018 and 2019 on Ubuntu, FWIW. Used alien as well (alien --install --scripts or something the like. Seem to remember also --target=i386 to force the installation of some component). Have not yet installed a 2020 so can't say, but is there chance that you skipped one rpm?

Edited by ensegre
i386
Link to post
Share on other sites

I have checked the LabView version and it was the full version not the pro version. After installing the pro version appbuilder works just fine.

Here is how i installed it using alien and dpkg.

mount lv2020pro-linux.iso /media/cdrom0
cd /media/cdrom0/
sudo mkdir /home/ll/Downloads/Software/labviewpro
sudo cp -r * /home/ll/Downloads/Software/labviewpro/
cd /home/ll/Downloads/Software/labviewpro/
sudo rm ni*i386.rpm
sudo alien -k -c *.rpm
sudo -s
dpkg -i labview-2020-core_20.0.0-1_amd64.deb
dpkg -i labview-2020-desktop_20.0.0-1_amd64.deb
dpkg -i labview-2020-exe_20.0.0-1_amd64.deb
dpkg -i labview-2020-pro_20.0.0-1_amd64.deb
dpkg -i labview-2020-ref_20.0.0-1_amd64.deb
dpkg -i labview-2020-rte_20.0.0-1_amd64.deb
dpkg -i labview-2020-help_20.0.0-1_amd64.deb
dpkg -i labview-2020-examples_20.0.0-1_amd64.deb
dpkg -i labview-2020-appbuild_20.0.0-1_amd64.deb
dpkg -i lvsupport2020-vianalyzer_20.0.0-f32_amd64.deb
dpkg -i ni*.deb

I want to thank everyone for their replys.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By javier_r
      VIPM.io now allows you to post LabVIEW Resources, Ideas, and Tools. For example, you could post a link to a video tutorial or blog article about a package. You can also post ideas, like feature requests or new tools. Best of all, package developers are notified when you post your ideas and resources, and you can comment and discuss posts with the community. Take a look at this video to learn more: https://www.vipm.io/posts/664960df-f111-4e13-989a-24be8207182d/

    • By Shuvankar Das
      I want to connect My ccd camera with labview. The details of my system is given bellow. I cannot connect it please help   OS:  WINDOWS 7, 64bit   LabView Run-Time 2013(64-bit) NI-IMAQ 4.8 NI-IMAQdx 4.3   Camera: QICAM Monochrome Cooled (QIC-F-M-12-C) Model QICAM Resolution 1392 x 1040 Sensor 1/2" Sony ICX205 progressive-scan interline CCD Pixel Size 4.65 x 4.65µm Cooling Type Peltier thermoelectric cooling to 25˚C below ambient Digital Output 12 bit Video Output FireWire (IEEE 1394b) Max. Frame Rate 10 fps full resolution @ 12 bits Pixel Scan 20, 10, 5, 2.5MHz Mount Type C-mount optical format  
       
    • By javier_r
      Hello everybody!
      Wondering how many people have tried the new vipm.io site. We have added a ton of features to make it easy to Discover LabVIEW Tools and there are some cool ones coming soon.
      Check it out and let me know what you think 😀
       
      Javier

    • By DigDoug
      CLA_ATM_QMH_PRACTICE.zipHi Folks,
       
      I'm taking the CLA exam in a few weeks and would like some feedback on the solution I put together (attached). A few specific questions:
      Can I dump tags in the VI Documentation of the VI like I did in Error Handler - Console Error.vi and get credit since there are instructions for developers to complete this work? This would be my strategy if I run out of time. 
      Does this seem like a passing solution? Why/why not?
      Where do you think I would lose the most points in this solution?
      Any other feedback on this exam or general strategy tips are greatly appreciated!
       
      Best Regards,
      Aaron
    • By David_L
      Hey all,
      (Cross-post from ni.com forums)
      We have a LabVIEW application, which has a LabVIEW-based Installer.  This LabVIEW installer is called from within another Inno installer (since our main Inno installer pulls together multiple components, most of them not LabVIEW).  Whenever this Inno installer ends, it always asks the user to restart their PC, even if the LabVIEW installer was cancelled.
      I narrowed it down, and it's reproducible with only the LabVIEW installer, so it's definitely LabVIEW installer's fault.  According to Inno's help documentation, "if a program executed in the [Run] section queues files to be replaced on the next reboot (by calling MoveFileEx or by modifying wininit.ini), Setup will detect this and prompt the user to restart the computer at the end of installation."  However, as stated above, this dialog is triggered even if the LabVIEW installer was cancelled and wrote no files.
      Now, the above linked documentation refers to a flag I can put in my installer script to ignore this restart dialog, but it's a global flag, and I would like my other installers to still make use of this handy restart dialog if necessary. Unfortunately it seems LabVIEW installers trigger this even if not actually necessary.
      Has anyone seen this before? Any ideas how to make my LabVIEW installer NOT muck around with the MoveFileEx or wininit.ini stuff if/when it's not actually needed?  Attached is a LabVIEW project and Inno Installer script which easily reproduces the problem.  To reproduce:
      Extract the attached .zip Open test.iss in Inno Setup and click the "Run" button Alternately, just run the built installer under "\Output\test_inno_installer_9.99.0.0.exe" Click Next on 'Select Components' dialog Click Install on 'Ready to Install' dialog When LabVIEW installer pops up click Cancel, then yes (you're sure) See the Restart dialog Thanks!
      David_L
      InnoLabVIEWBug.zip
×
×
  • Create New...

Important Information

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