LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

exe building makes small file


@Florian.Ludwig wrote:


Why? Why do you need 32 bit executables when it works on 64 bit?


IIRC our main issue was that we use 3rd party dlls which are 32 bit, and I was told those won't work in a 64 bit application.


Yes, they won't work. And that is a 64 bit showstopper.

 

Of course the 3rd parties will need to convert at some point.

 

16 bit (yes, 25 years ago) did coexist with 32 bit for a few years, but eventually maintaining both is just too expensive (for everybody).

 

On the bright side: it's unlikely we'll be around when the switch to 128 bit happens.

0 Kudos
Message 51 of 55
(486 Views)

wiebe@CARYA wrote:

On the bright side: it's unlikely we'll be around when the switch to 128 bit happens.

You call *that* a "bright side"?!?   Yikes!

 

 

-128-bit Kevin P

💀

 

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 52 of 55
(478 Views)

@Kevin_Price wrote:

wiebe@CARYA wrote:

On the bright side: it's unlikely we'll be around when the switch to 128 bit happens.

You call *that* a "bright side"?!?   Yikes!

 

 

-128-bit Kevin P

💀

 


Well, it grows exponential, so it will take at least thousands of years. It probably won't happen at all, as the current CPU architecture won't last that long. If even humanity lasts that long.

 

16 bit 65,536

32 bit 4,294,967,296

64 bit 18,446,744,073,709,551,616

 

 

 

 

0 Kudos
Message 53 of 55
(473 Views)

@AlexanderKhodarev wrote:

NI support wasn't helpful too much. I can understand it in a way. They need a source code to test. But in reality you can just generate bunch of random VIs (i assume) and create project which pushes 3.5GB during build time and 100+MB in exe size and get same results (failed builds or builds which end up with 144KB file).


I don't understand it. I've given them the crash reports, dump/build logs etc and they should be able to extract the information needed to at least steer me in the correct direction, but the answers I got were, well have you tried the suggestions on this page? (Points me to a generic NI support page recommending to not use local variables and make sure I'm using a producer consumer design.)

0 Kudos
Message 54 of 55
(457 Views)

One more observation: Being able to build can come and go.

I previously mentioned that the slow machine has a much better ratio of normal to small executables.

Currently my fast work machine does it every other attempt (which is excellent, given the state of things).

It currently works like this:

 

1. I update the code from the repository.

2. Clear compiled object cache.

3. Open everything to compile.

4. Close and open the Project (because seemingly it never works when anything besides just the project was open).

5. Attempt to build unsuccessfully.

6. Close and open the Project.

7. Build succesfully.

0 Kudos
Message 55 of 55
(416 Views)