Search the Community
Showing results for tags 'compile'.
I’m a big fan of JKI VIPM, and I’ve been usen Source code control with labview for some years (First with mercurial and now with GIT). Following the good practices with SCC and LabVIEW I always check the separate compiled code from vi to avoid unwanted changes on Vis. In the other hand I’ve read that the performance of labview is better with the compiled code in the VI. Besides that the labview IDE does not allow you clear compiled cache of some of your vis, you have to delete all the compiled cache…When I have some compilation errors and I delete the compiled cache It takes a lot of time
Hey guys, I am currently having some issues with a FPGA program with Softmotion not compiling. We are running out of options in terms of how to get this FPGA program compiled. So my question is does compiling on Linux have a different probability of compiling FPGAs? I have heard that Xilinx Compiler is meant for Linux so it runs more efficiently and faster, so I was just wondering if the compile method was different as well
I'm attempting to compile an FPGA project for an R series card to use in Veristand 2011. I used the FPGA creator wizard to get the basic template and modify my IO as directed. When I attempt to build the project, I get the following error. 'LabVIEW: Generic file I/O error.' ========================= NI-488: I/O operation aborted. Error 6 occurred at Write to Text File in niFpgaCompileWorker_SaveStatus.vi-> niFpgaCompileWorker_Status_Publish.vi-> niFpgaCompileWorker_GetStatus.vi->niFpgaCompile_Worker.vi:1 Possible reason(s): LabVIEW: Generic file I/O error. ===============