Jump to content

x y z

  • Posts

  • Joined

  • Last visited

  • Days Won


x y z last won the day on September 7 2017

x y z had the most liked content!

LabVIEW Information

  • Version
    LabVIEW 2010
  • Since

x y z's Achievements


Newbie (1/14)



  1. Sorry for late reply, I didn't see any alert from this topic ... my bad So I've found an other solution/hacking and it is similar as you mentioned, but at lower level of building process. #1 Create "Smart Device" C++ project in Visual Studio 2008. Choose SmartPhone 2003 (ARMV4) SDK (this is an another story but in short Labview2010 need for this, see: Arm vs. Thumb) #2 DLL or LIB project type is fine (DLL project won't linking because of missing NumericArrayResize reference but its ok we need only OBJ files of the project). #3 Build the project! OBJ files are generated as intermediate files between compiling and linking phase of the building process. #4 Grab all OBJ files and attach them to LabVIEW Touch Panel project tree #5 Add the OBJ files as "Additional files" in LabVIEW project -> Touch Panel -> Build Specifications -> "Source files" -> "Additional files" #6 Build Touch Panel project, it should compiling successfully. This trick made the LabVIEW linker to link the referenced functions (NumericArrayResize) between my code and the LabVIEW code. In other word I've injected my codes as OBJ files into the LabVIEW building process. I've used this method because it is pleasure to work with Visual Studio and test the code on HMI. When everything is ok with C++ code, then just build VS SmartPhone LIB project and use it in the Labview project.
  2. [...]The LabVIEW PDA Toolkit is not supported anymore [...] Just for the record: I'm working with LV2010 + Touch Panel module (Windows CE 5.0) the device is a Windows Embedded Compact 7.0 (ARM Cortex-A8) based HMI. So what you suggest in your post it would be a cool idea, but as you suppose, LabVIEW Touch Module build a single EXE file. When I looked into the EXE with hex editor there wasn't any sign of NumericArrayResize function and this is normal for EXE. That's why the example code above not working. Two way left: Before DLL call, presize buffers and strings in LabVIEW and check the size limits in DLL DLL callback functions to give back buffers and strings to LabVIEW to resize them with the LabVIEW memory manager and give them back to DLL (overkill) I've chosen solution #1. Thank you for your help!
  3. Hello! I'd like to resize LStrHandle string in a C++ based DLL ... which is perfectly working on desktop Windows (ex.:Win7 32/64 bit) platform by include "extcode.h" and linking "labviewv.lib", with calling "NumericArrayResize" function. BUT I'd like to do the same on Windows Embedded Compact 7.0 with ARM(Cortex-A8). When I build the DLL project on "Smart device / WindowsCE" platform it compiled successfully but the linker stopped because "NumericArrayResize" is unresolved symbol ... I think the reason is that the "labviewv.lib" generated for x86 architecture not for ARM. So my question is: Is there any libviewv.lib for ARM platform?
  • Create New...

Important Information

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