Jump to content

Yaw Mensah

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0

About Yaw Mensah

  • Rank
    Active

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since
    2017

Recent Profile Visitors

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

  1. Thank you very much. Do you know a reference targeting Labview on linux for this matter. Wouldn´t i avoid this whole mess by only using an Opencv version with a c api?
  2. Does anyone know the exact version when opencv droped the c api.
  3. Calling a function or use of a datatype from <opencv2/opencv.hpp> result in a name mangling or undefined variable issues.
  4. I'm using labview on Linux, which does not support dotnet. So EmguCv is not an option. I thought about only using the C API in opencv to avoid name mangling and undefined variables issues, but the later version of opencv doesn't support C API. i'm now stuck at figuring out how to call the c++ function in a c calling conventtion. example code: #include <stdio.h> #include <opencv2/opencv.hpp> using namespace cv; using namespace std; extern "C"{ int displayimage() { Mat image(400,400, CV_8UC3, Scalar(0,0,255)); image = imre
  5. I am trying to create to shared library with opencv to acess a picture. I have no experience on this topic. If anyone have a referece or example-code that can help me develope an understanding i would be very thankful. Rigth now i have created a shared libray to display a picture. But i get the error that Mat variable is not defined when it is called in labview. I will be thankful for any suggestions.
  6. Thank you very much. Call Library Function Node doesn't change the name and calls the fuctions as desired.
  7. I have created a simple shared library with an add function. When I try to call it with the Call Library Function Node, it always change the name, e.g. add() to Z2addii(). In the Error is always the same error. Call Library Function Node 'libtestshared.so.Z2addii: not found in library. When i change the functionname in the shared library to Z2addii the Call Library Function Node then calls the Z3Z2addiiii. But when i compiler a c-programm which uses the shared library i get the desired output. I will be grateful for suggestions.
  8. It works now. In Addition to installing everything i needed libxinerama1:i386 und libgl1:i386. Those two can be installed with apt-get install. Thank you for your suggestions.
  9. Is there a way to convert the 32-Bit rpm to deb so they can installed?
  10. file /usr/local/JKI/VIPM/vipm /usr/local/JKI/VIPM/vipm: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.33, BuildID[sha1]=ff35d7adc7d9ef4e1ee0b41f6d67085e2c22dbe7, stripped file /usr/local/JKI/VIPM/support/*.so /usr/local/JKI/VIPM/support/lvanlys.so: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, stripped /usr/local/JKI/VIPM/support/lvzlib.so: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, with debug_info, not stripped After tha
  11. In the folder there different files for different architecture. For example I would delete nicurli-15.1.0-f0.i386.rpm but install nicurli-15.1.0-f0.x86_64.rpm and nicurli-15.1.0-32-Bit-f0.x86_64.rpm. If i leave nicurli-15.1.0-f0.i386.rpm there alien report wrong architecture and doesn´t convert.
  12. I am trying to install the package manager, vipm-17.0.2018-linux, for LabView on Debian Linux and it is a total mess. I copied the folder /JKI and all the contents to /usr/local. And installed the rpm files in the LabVIEW2015SP1RTE_Linux folder by converting them with alien to deb files. I removed the 32-Bit rpm files before converting them. When i try to execute run it doesn´t find the libraries. I will be grateful for any suggestions.
  13. 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.
  14. 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.
  15. 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.
×
×
  • Create New...

Important Information

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