Search the Community
Showing results for tags 'compiler'.
Found 4 results
Hello I have received a LabVIEW dll and the corresponding header files so that I can send a trigger to a skin stimulation device. when I use the loadlibrary command in my Matlab script, I receive these two errors: "We don't know the Compiler" and "We don't know the ProcessorType architecture" Which means while reading the "platdefines.h", the Compiler and the ProcessorType does not match the ones listed in ifs. I have set c++ compiler to visual studio 2015 in Matlab. (also tried MinGW). the system I`m using is Windows 10 (tried on 7, too), 64bit. I read somewhere that manually defining the ProcessorType and the compiler might solve the issue. But the problem is I Don`t know what they are. (when these two conditions below are not accepted.) #elif defined(_MSC_VER) || defined(_NI_VC_) #define Compiler kVisualC #elif defined(_M_X64) #define ProcessorType kX64 -------------------------------------------------- How should I find out the ProcessorType and the compiler I have? I`d be EXTREMELY THANKFUL for any solutions you can think of. P.S.1 I attached all the headers and the Matlab error.jpg P.S.2 The code seems to work fine on manufacturers system with Matlab 2011. so it may be Matlab-related, but I don`t get how since the error is from platdefines header file. extcode.h fundtypes.h hosttype.h ILVDataInterface.h ILVTypeInterface.h lv_epilog.h lv_prolog.h platdefines.h STIM.aliases STIM.dll STIM.h STIM.ini STIM.lib
I was mucking around in General Error Handler.vi today and noticed a weird subVI with a really intersting comment inside. Thought I'd share it with the crowd, since it applies to time-critical processes, thead swapping, and general compiler insights.
Did you happen to catch the announcement a while back (LV2010 era) that LabVIEW source was being compiled to DFIR (DataFlow Intermediate Representation) and then to LLVM IR (Low Level Virtual Machine) before being compiled to target-specific machine code? Let's look at LLVM a moment; it's exciting. This acronym is not just some LabVIEW R&D mumbo jumbo; the LLVM compiler is something that has cause quite a stir in the programming community for some time now. In 2012 -- two years after NI R&D publicly announced that LabVIEW was leveraging LLVM -- LLVM won the ACM Software System Award. Who else has won this yearly award given to only one project? Ever heard of, say, UNIX? Java? The World-Wide Web? Eclipse? Apache? Shite -- i guess this makes LLVM A Big Deal. A couple top-notch articles I've caught recently include: "IR is better than assembly": https://idea.popcount.org/2013-07-24-ir-is-better-than-assembly/ "Kaleidoscope and the Lexer": http://llvm.org/docs/tutorial/LangImpl1.html And my favorite, for the dear memories and sheer genius of this guy: "Statically Recompiling NES Games into Native Executables with LLVM and Go": http://andrewkelley.me/post/jamulator.html This stuff is blowing my mind, and I'm really glad to know LabVIEW has hitched its wagon to LLVM. Keep it up, Compiler Team -- chime in here and tell us more.
Hi all - I've just posted a tool to analyze compiled code complexity of VIs in a project at http://forums.ni.com...12/td-p/2121692. Note that compiled code complexity is a new feature in LabVIEW 2012, and so this won't work with earlier versions. I'd be happy to answer any questions here or on the forums! (is it kosher to spam LAVA with links to forum posts? If not, my apologies...) Greg Stoll LabVIEW R&D