Mass Compiler Error 13

[medvall]

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

medvREMall@tomREMlab.biREMz

[Albert.Geven]

It could have been labview dll's but obvious are not, so you don't have a problem.

[medvall]

OK, they are LabVIEW dll's generated from VI's. Everything seems to be working regardless, but the error is not customer friendly. Any help appreciated.

Best wishes, Marcus

[Albert.Geven]

Hi Marcus

If these dll's contain source they can be masscompiled, otherwise not. Normally the source is not included! Only to make debugging possible.

[medvall]

Hi Albert,

Thanks for the info - so there is really no way we can fix the problem then (i.e. do something to make the message disappear)?

Best, Marcus

[Albert.Geven]

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.