MASS COMPILING

IN PROJECT BUILDER, IS THERE WAY TO "MASS" COMPILE ALL FORMS,RPTS...ETC WITHOUT HAVING TO COMPILE INDIVIDUALLY?

You're not going to want to mass-compile the VIs in the LabVIEW 7.0 directory to LabVIEW 7.1.1. That will make you unable to open them in LabVIEW 7.0. By the way, a VI compiled with LabVIEW 7.1.1 can be opened with LabVIEW 7.1.
Joe

Similar Messages

LabVIEW classes and mass compile

Just wondering if anyone out there has found any problems mass compiling LabVIEW classes, as I am having what appears to be totally un-resolvable issues - I get a list of VIs that either say BadsubVI or BadVI all of which I have verified are error free.
The only thing I can round it down to is the use of the lvclasses, and in particular the fact that I'm making extensive use of the inheritance functionality, and also a few override vi's.
It wouldn't be such an issue except that I'm calling some of these vi's from TestStand, and am unable to get a deployment to work without a successful mass compile.
Appreciate any responses,
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England

I'm not sure if it's the same problem but I had a vi that would compile into an unrunable exe. I found the problem by mass compiling the project, which came up with a bad vi and bad subvi's that used that vi. Turns out my problem was that I had two classes with the same name (even though they were in separate lvlibs). And renaming one corrected my problem. LabVIEW 8.5 gives a warning and renames the compiled vi's (so if you could try 8.5, that might help you find the problem quicker assuming it's related). It seems to me that the name spaces provided by lvlibs go away when compiled into an exe or by the mass compiler (It may just affect lvlclasses).
Matt

LabVIEW 8.0.1 on Windows 8 wants to mass compile every time I start it?

My Windows 7 machine took a dump and I installed LabVIEW 8.0 on a new Windows 8 machine. I then installed the 8.0.1 upgrade and did the mass compile. I then installed NIVPM and attempted to install the openG package which some of my vis depend on. Only a few of the openG modules installed without dependency issues or somesuch. Now every time I start LabVIEW it is as if I never did the mass compile and it wants to do it all over again. I don't recall having any such issue when I installed labVIEW in Win7 (or Vista, or XP). Am I missing something? Can someone help... please???
In case it matters the machine is an HP Pavillion G7-2240US laptop, Intel Core i32370M @ 2.4 GHz, 6.00 GB RAM

OK, I get it. You are irritated that you can't do something you wanted to do. I can't understand what bug you are talking about. LV8 doesn't run on Win8? That's not a bug. By your logic I should be able to dig out the old V4 disks I have laying around and run them on my Win7 computer. Or better yet, I still have an old Mac488 GPIB interface box made by IOTech. Should I be expecting NI to come out with DAQmx drivers for it? They did after all buy out the company.
I got two words for you: obsolete happens. V8 was a good version in its day, but its day was 6 years ago. Someday LV2013 will be obsolete - heck someday you will be obsolete. It just happens, so my suggestion is to go buy yourself a pair of big-boy pants and stop whining.
Mike...
PS: If you found any of what I just said offensive, please reread my last suggestion.
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Mass compile in Windows 7 on SimpleErrorHandler.vi

Hello,
i wrote some action in Labview 2011 that i want to use in Teststand with labview-runtime.
But some of them are not working and cant be loaded in Teststand. So someone told me to run a mass-compile.
I did this several times (also on complete drive c but with no luck.
Now i found out that only the vis that are using the "Simple-Error-handler.vi" are not working and cant be loaded.
When i delete this vi from my VIs then i have no problems any more.
So i opened the SimpleErrorHandler.vi manually in Labview and selected "Save All".
Then i get a popup:
Cannot save VI "FXP.xctl:fxpInit.vi"
The VI already exists and you do not have permission to replace it."
How can i resave it? I think the SimpleErrorHAndler must be also saved in Labview 2011 to be runable in the runtime2011
Thanks for help

Just to close the Circle:
This Thread deals with the same Problem:
http://forums.ni.com/t5/NI-TestStand/Vi-not-running-when-using-NI-s-SiimpleErrorHandler-vi-TS2010/m-...
Regards!
Moritz M.

Internet Toolkit for G5.0 crashes Labview 8.2 during Mass Compile

I have just received my Labview 8.2 update and installed it my system along with all my toolkits. When I tried to Mass Compile Labview 8.2 directory I found that it would crash labview consistantly as shown in the attached image.
I traced this to the vi's supplied with the Internet Toolkit for G5.0.
The workaround is ...
1. Re-installed the Internet Toolkit for G5.0 into Labview 8.2
2. Mass Compiled ...\project\_config\authcfg.llb using Labview 8.0
3. Mass Compiled ...\project\_config\authcfg.llb using Labview 8.2
and there wasn't any more Labview 8.2 crashes during mass compile. As Labview 8.0 was able to mass compile the internet toolkit vi's without crashing I am suspicious that Labview 8.2 might not be completely compatible with Labview 5.0.
I posted this just in case anyone else sees a similiar issue.
David
Attachments:
Labview 8.2 Mass Compile Crash with Internet Toolkit.png ‏34 KB

David,
I was able to reproduce the crash mass compiling authcfg.llb or just trying to open the VI named 'Directory Configuration'. That code is saved in LabVIEW 5.0.1 and must have something that LabVIEW 8.2 chokes on, I'll have to get someone to investigate it. Your workaround of saving that .llb or even that one VI in 8.0 first (or probably even 7.x) is the only way I see around it with 8.2.
I do want to mention that in Q1 2004 we released version 6.0 of the Internet Toolkit and it does not exhibit this behavior. So the official solution for this crash is to upgrade to the latest Internet Toolkit.
Kennon

Mass Compile "Bad VI" & "Bad SubVI" errors, but with no apparent errors.

I am using LabView 8.5, FIRST Robotics Competition Edition, targeting the Compact RIO.
I am getting Mass Compile "Bad VI" & "Bad SubVi" Errors, in my own code, but with no apparent errors in the vi's themselves.
#### Starting Mass Compile: Mon, Jan 19, 2009 11:59:34 PM
  Directory: "C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Robot.lvproj"
  ### Bad VI: "Autonomous Independent.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Autonomous Independent.vi"
  ### Bad VI: "AcceleratingArcadeDrive.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\AcceleratingArcadeDrive.vi"
  ### Bad subVI: "CrazyIvan.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\CrazyIvan.vi"
  ### Bad subVI: "Teleop.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Teleop.vi"
  ### Bad VI: "Autonomous Independent.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Autonomous Independent.vi"
  ### Bad VI: "AcceleratingArcadeDrive.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\AcceleratingArcadeDrive.vi"
  ### Bad subVI: "CrazyIvan.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\CrazyIvan.vi"
  ### Bad VI: "AcceleratingArcadeDrive.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\AcceleratingArcadeDrive.vi"
  ### Bad VI: "Autonomous Independent.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Autonomous Independent.vi"
  ### Bad VI: "AcceleratingArcadeDrive.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\AcceleratingArcadeDrive.vi"aa
  ### Bad subVI: "CrazyIvan.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\CrazyIvan.vi"
  ### Bad subVI: "Teleop.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Teleop.vi"
  ### Bad subVI: "Robot Main.vi" Path="C:\Documents and Settings\Acshi\My Documents\LabVIEW Data\Robot\Robot Main.vi"
#### Finished Mass Compile: Mon, Jan 19, 2009 11:59:46 PM
Since some of these reference each other, this is the block diagram of one that doesn't reference any other erroring vi's.
What can I do to fix this?
Attachments:
BlockDiagram.png ‏29 KB

Interesting... It must have timed out before the temporary image did, and so I did not noticed a problem until I returned.
Regardlessly, I have found the error.
Errors did exist in my VI's, In particular, one of the subVi's I called in the VI shown happened to be private only, and so couldn't be used -- now I've just made a public version for my personal use. But LabView would not show me the actual errors unless I force-ran the the program, I really don't know why I had to do this, but when I did, it showed me a nice little dialog with my errors in it.
I am confused, as when I did normal runs, it would simply complain that the VI's were invalid and would not permit the run.
Very odd.

Mass compile crashes LabVIEW 2010

Before I go ahead and call the support line
Pentium 4
2.8GHZ
2GB RAM
XP 32 bit
Anyone have issues mass compiling an application code from 8.6.1 to 2010 SP1 whereby it would seem to work fine for quite awhile then crash?
I tries no cache on the VI and all other items are off.
It seems to happen even in subdirectories of the application.
I just installed 2010 SP1 and the device drivers and when I look at them in isolation they seem to be installed correctly.
I can also load the 8.6.1 application
Im just wondering if Mass Compile is running out of memory and is it known issue or am I discovering something.
I will attempt to log results on the next try.

Hey guys, this is Paul with Applications Engineering at NI.
I have reviewed your issues, asked around, and have a couple tips and questions.
First, if there is any chance you could post your project in a zipped format, then we could examine it on our end and see if we experience the same issue, which would make it easy to file a CAR on. If you are wary of posting your code publicly, you can PM me, and we can work out a way to upload it to our FTP server that only NI employees can access.
richjoh, in your posted Mass Compile screen, I see a VI being flagged as bad. When you open this VI on it's own do you experience this problem? Can you locate in that VI where it calls the NanoMsg.lvclass?
Second, to either of you, were the controls and lvclasses mentioned still referenced in your projects anywhere? Were they included in the dependencies? If not, once you restored these files into the project, find them in the
dependencies, right click them, choose "Find">"Callers". Where they still being called anywhere?
Alternative to your solutions, have you considered creating a new project and adding all of your VIs into the new project? I have seen this resolve upconverting issues in the past.
Paul Davidson
Sound and Vibration Software Staff Product Support Engineer
National Instruments

How to execute "Mass Compile" in my own Installshield?

I have to create my own distribution with
Installshield.
I don't know how to run automatically the Mass Compile at the end of the installation procedure.

You will need to create a VI that calls the "Mass Compile" VI Server Application Method. Have install shield launch this VI via a command line and have the VI set to "run when opened".
Good luck,
Jim

"red X" error during mass-compiling installing labview upgrade 6.0.2

I always get a "red X" error during installation of the LabVIEW 6.0.2 upgrade.
The mass compiling always fails.
The environnement is an italian version of W98.
Salvatore Randazzo
[email protected]

I would try compiling one directory or .llb at a time instead. See if you can isolate the problem.

MAC V2.2 conversion to V3.1 mass compile cant find certain VIs

I have some MAC LabView 2.2 files that I need to convert to Labview 2012. I have started using the conversion tool to go to Version 3.1.
During the mass compiler process it tells me that it cannot find a lot of VIs such as “Open Folder”, “Open Files”, etc.
I am having the same problem as the person in this thread:
http://forums.ni.com/t5/LabVIEW/I-try-to-convert-LAbview-2-2-VI-to-Labview-3-1-for-MAc-using-the/td-...
I tried what Dennis’ suggested by saving files such as “Open File+.VI” from Version 3.1 as just “Open File.VI” but when I select the newly saved file it doesn’t take; it just re-prompts me for the VI again.
So can someone explain further what I need to do to find these VIs? Or get the ones from Version 3.1 to work?
Thanks
T

T,
The problem you run into in converting VIs that old is that some of the functions and VIs used in the older version simply do not have any direct equivalents in the newer versions. You have to go in and reprogram things to get the same functionality with the new VIs.
Do you have an old Mac on which to run the LV 2.2 version? If so, I would spend enough time with that version to document what the program does and then write a new program in LV 2012 with the same capabilities (plus all the new things someone will have decided to add). Make backups and print out all the diagrams. Just in case.
I am currently in the process of rewriting a program which is currently in LV5, LV6, and LV8.6 to LV 2012. This program started out in LV1.2 and was rewritten in 2.2.1 or 3 and then converted to 5 and upgraded a few times. Event though I was the programmer in all the versions, very little of the current version except for some user interface items will be carried forward to the new version.
Lynn

Command line: Mass compile and LLB Conversion

Using LabView 8
Using a script (Perl or VBScript) I would like to extract some VI from our source control,
mass compile them to be to the current LabView version and then create a LLB from that directory.
The need for this is to have a synchonisation between 2 applications.
Since this needs to be done from a script, I need a way to perform this from the command line.
(The other solution we have, is to perform this manually every time a modification is made to the original files,
But sometimes memory can be defective and then .... )
Any suggestions, ideas...
Thanks
EricG

Eric,
That sounds like quite an undertaking, but I think you might be able to implement it (or at least most of it). LabVIEW does not have command line arguments for all that you want to do, so I would recommend building a VI that does what you want and then building that VI into an executable that utilizes command line arguments.
In this VI, opening VIs and mass compiling them can be accomplished through VI Server in the form of an Invoke Node -- these functions are methods under the Application class. Bear in mind that mass compiling can only bring VIs forward in versioning, not backward. For the LLB functions, you can use the Libraryn VIs that ship with LabVIEW -- they are "hidden" in the LabVIEW root directory under vi.lib/Utility/libraryn and are pretty intuitive. As far as the source code control, you are on your own, as that will be dependent on the specific SCC software you are using and will most likely require using ActiveX.
Once you have a VI built that does everything you want and you are ready to build it into an executable, you will want to configure it to accept command line arguments. There is a great online Knowledgebase on this subject, which I have linked here. And of course, if you run into any specific problems along the way you can get help from this great online community!
Best of luck!
E. Sulzer
Applications Engineer
National Instruments

LabVIEW crashes during mass compilation every time

Hello All
I have installed a new LabVIEW 7.1 from February on Win XP.
Every time when I try to mass compile LabVIEW, after few files it crashes, and only one thing I can do is to send a report to Microsoft.
It looks like it crashes in a moment when it can not find a subvi in the directory structure.
What is wrong with it?
Thanks in advance.
Pawel

I hope you are not trying to mass compile the entire LabVIEW directory. I will definately choke on several of the files it will find. If you have upgraded to 7.1.1, you should mass compile the vi.lib, instr.lib, user.lib and examples directories.
You could also have an error with the Paths settings. If it is searching an invalid path to find a subvi, that might cause the problem.
I suggest that you start small and try a single subdirectory like user.lib, then move on to instr.lib, then examples.
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

Basic: what is mass compile (LV updater 6.0.2)?

I received LV updater 6.0.2 and when I run it, it asked whether I wanted to perform mass compile. What is this? what are its advantages/disadvantages?

Advantage: all of the VIs are updated at once.
Disadvantage: takes a long time.
Each of the VIs that you open that are in a previous version will ask if you want to save them in teh new version when you close anyway. I think that not updating and just doing them "as you use them" is the better way to go (for saving time).
On the other hand, I told my computer to mass compile and then went home for the evening. Pick your time.
Rob

Mass compile dialog after saving vi's on Perforce

I have been receiving errors saving vi's to Perforce which prompted a mass compile. Upon completion, I received the attached dialog box. Can anyone give me direction/suggestions how to proceed?
Thank you.
Attachments:
MassCompile09Aug2013.txt ‏551 KB

It appears that LabVIEW is having trouble locating the Visa. When performing the mass compile do you have access to edit all the Visa and sub Visa that it is trying to access? Also, you could also try saving the project onto your desktop with all the files, mass compiling, and then individually moving them into Perforce but that would be tedious.
Jesse S.
Applications Engineer
National Instruments

Mass Compiler Error 13

Hello,
We are mass compiling a solution on client machines. To do this we just select the current base directory and hit mass compiler. There are dll's, vi's and vit's in various subfolders that we need processed. This all seems to work fine, but we are getting the following error:
#### Starting Mass Compile: Fri, Apr 07, 2006 5:28:42 PM
Directory: "C:\TOMVIEW"
CompileFolder: error 13 at C:\TOMVIEW\dll\gateway.dll
CompileFolder: error 13 at C:\TOMVIEW\dll\gatewayfc.dll
CompileFolder: error 13 at C:\TOMVIEW\dll\gatewaygJ.dll
#### Finished Mass Compile: Fri, Apr 07, 2006 5:30:06 PM
The folder dll contains 28 different dll's (that are all referenced from various VI's).
Question 1: Why is it doing anything at all with these dll's?
Question 2: How can we prevent this error from occuring (it does not seem to have an effect anyway)?
Question 3: Do we have a problem at all?
Best wishes, Marcus
Tomlab Optimization Inc.
http://tomlab.biz
[email protected]
Marcus M. Edvall
Tomlab Optimization Inc.
855 Beech St #121
San Diego, CA 92101-2886
USA
web: http://tomopt.com
e-mail: [email protected]
Office1: (619) 203-2037
Office2: (619) 595-0472
Fax: (619) 245-2476

Hi Marcus
The easiest solution is to move these dll's to another directory, next to the math compile path.
The second best option is the filtering of the messages.
The best solution is that someone within NI fixes this e.g. by giving you the opportunity to accept mass compile errors of a certain kind.
At last somebody can write a new mass compile for you.
In fact it is nothing more than traversing the directory tree and trying to compile each vi.
I hope somebody that has the time and knowledge to help you will pick this up.
greetings from the Netherlands

MASS COMPILING

Similar Messages

Maybe you are looking for