Jump to content

Can the automatic building be switched off?


Recommended Posts

Hi,

 

We are evaluating the use of VIPM for the installation of a sizable library of Labview code. This should make it easier for developers to start projects that make use of this library (framework).

The first impression is very positive, the tool really does a lot for you. But that (big black box :-) brings up some questions...

- What is it doing precisely?

- Why does it do it? (e.g. guaranteeing integrity?)

- Does it really need to? (we have some degree of control over the developers environment ourselves...)

- Can you switch of some of this functionality? (to save time, to bypass build errors that would appear late in the project, ...)

 

Specifically the (mass) compiling of code: Both during the building of the package and during installation, the sources are compiled (which takes some time)

To clarify: our first approach to this library installation was rather a copy/paste operation, like a generic installer...

Can this building be disabled or are there compelling reasons why this should always be in place?

 

A related question: are project .lvproj files inside the source directory being analysed by VIPM? Does it make a difference to include/exclude/alter these files from the source directory? Is there a difference between removing them physically versus excluding them from the build in the VIPM tool itself?

 

Frank

Link to comment
Share on other sites

Can this building be disabled or are there compelling reasons why this should always be in place?

I assume you mean the mass compile step? This cannot be turned off currently. Can you describe your use-case and why you would want to disable this?

However, this can be turned off for the installation process. This is located under Tools>Options>General>Mass Compile VIs after package installation.

A related question: are project .lvproj files inside the source directory being analysed by VIPM? Does it make a difference to include/exclude/alter these files from the source directory? Is there a difference between removing them physically versus excluding them from the build in the VIPM tool itself?

The lvproj file is not currently being used by VIPM. You can exclude it from within VIPM (easier) or you can manually delete it from the source folder (harder).

 

 

 

Link to comment
Share on other sites

Thanks for the quick response! :-)

 

Can you describe your use-case and why you would want to disable this?

 

It's not yet a hard use case but I'll try to formulate it anyway :-)

While I was experimenting with making an installer for a stripped version of our library, VIPM stopped with some (for me) obscure errors (if I can reproduce it, I'll post the error numbers). making an installer for the whole project works fine. So my fear is I'd get stuck in the stripping process (and of course there's some time pressure as always :-)

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.