LabWindows/CVI Idea Exchange

About LabWindows/CVI Idea Exchange

Do you have a feature idea for how to improve LabWindows/CVI? Submit and vote on ideas now!
  1. Browse by label or search in the LabWindows/CVI Idea Exchange to see if your idea has previously been submitted. If your idea exists, be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click New Idea to submit a product idea. You should submit a separate post for each idea. Watch as the community gives your idea kudos and adds their input.
  3. Give kudos to other ideas that you would like to see implemented!
  4. NI R&D will review ideas that have been submitted and update the status.

Note: the LabWindows/CVI Idea Exchange is not the appropriate forum to submit technical support questions.

The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange. However, we cannot guarantee the implementation of any LabWindows/CVI Idea Exchange submission.

Top Kudoed Authors
User Kudos Count
1
1
cancel
Showing results for 
Search instead for 
Did you mean: 

Allow for smaller distribution kit sizes

As discussed here, distributing the code of

 

#include <ansi_c.h>
int main ( int argc, char *argv [] )

{
    printf ( "%s", "Hello world" );

 

generated in CVI2013 results in a distribution kit of 74 MB minimum...  Using the NI default settings results in 219 MB...

 

Yes, I do have TB drives, but I dislike bloated software.

2 Comments
Active Participant

I support this request.

 

Distribution kit sizes are relevant not only for downloading and storage, but also limit the ability to send it as an attachment, or upload it from an out-of-the-office situation like a hotel room or tethered connection. In those cases sub-1Mb/s upload connection speeds are very common, leading to 20-30 minute upload times  ... IF the connection does not time-out or get cut off.

 

Unfortunately, this is why I'm not using CVI 2013.

 

--Ian

Trusted Enthusiast

One quick and simple step towards this goal could be to change the default settings; right now, creating a new distribution has all LabWindows components selected, even if they are not used...

 

new_dist.png