Unused vi compiled into exe

[alex.]

When build exe, there seems some unused vi lib and .mun files been compiled into exe as attached screenshot.

It make the exe quite big, 24M. 

Any suggestion?

[TCPlomp]

There are two settings to change:

• Disconnect Polymorphic VIs and Typedefs
• Remove unused library (or class?) memebers.

Ton

[Ray.R]

As Ton suggested..

You can configure these within your build properties, under "Additional Exclusions".

R

Message Edited by JoeLabView on 02-09-2009 07:18 AM

[alex.]

Thanks,

After select option2(LV8.2), it is just half size(13M) after compiled.

But may I know what is the difference inside. If they are not in the exe, where are they.

Does the performance will be affected?

[TCPlomp]

No, with this option you have excluded non-used code from your executable.

Ton

[Ray.R]

I never paid attention to the fact that the additional exclusions screen was different for LV8.2 & LV8.5.  Interesting..

From LV8.2:

[NIquist]

Does anyone know of a good reason to compile all of the extra stuff? 

If the EXE can run without it, why wouldn't the App Builder default to making the installer as small as possible?

[Wiebe@CARYA]

"NIquist" <x@no.email> wrote in message
news:1234276808095-850101@exchange.ni.com...
> Does anyone know of a good reason to compile all of the extra stuff?&nbsp;
&nbsp;If the EXE can run without it, why wouldn't the App Builder default to
making the installer as small as possible?

Executables might call dynamic VI's. If the vi's interface with type defs,
it's easier to keep the type defs in the executable.

Same goes for the polymorphic vi's. If they are in the executable, the
dynamicly called subvi can use them, since they are already loaded into
memory. If you disconnect them, the sub vi can't find them, and you need to
provide them seperatelly.

There are other situations where you'd want to keep the original type def's.
For instance, if you do things with the type def information, like storing
and reloading it.

I'd say, in normal programs, simply disconnect everything. It *might* effect
the performance, but only for the better.

Regards,

Wiebe.

[alex.]

'If you disconnect them', where will they be placed, in which file format.

Thanks,

[RavensFan]

The disconnected stuff will still exist in your .VI's and the LabVIEW libraries.  The just won't be embedded in the compiled format of the executable.