32/64 builds

[Viper]

I'm in a position where I need to build win7x64 applications with LabView 11. I've installed 32 and 64 on the same machine. Will opening my application source in 64 screw things up.

1. Can I maintain a common code base for both 32&64 executables?
2. Can I just copy my inst.lib and user.lib folders into the x64 version?
3. Do I need to have separate inst.lib and user.lib folders for the two versions?

What are best practices for keeping source files current across multiple machines and multiple versions?

Norm

[crossrulz]

---

@Viper wrote:

I'm in a position where I need to build win7x64 applications with LabView 11. I've installed 32 and 64 on the same machine. Will opening my application source in 64 screw things up.

1. Can I maintain a common code base for both 32&64 executables?
2. Can I just copy my inst.lib and user.lib folders into the x64 version?
3. Do I need to have separate inst.lib and user.lib folders for the two versions?

What are best practices for keeping source files current across multiple machines and multiple versions?

Norm

---

Make sure you are using the "Separate compiled code from source file".  It is a setting found in the VI properties.  So now you can open the same code with both the 32 and 64 bit versions of LabVIEW.  Obviously, only one version at a time.  But with the separate compiled code, they shouldn't be recompiling your source VI.

[Viper]

Why should I care if it recompiles my source VIs. Yes the need to save ripples up through my application tree but the compile code is maintained in separate compiled object cache for the 32 and 64 bit versions isn't it? It just needs to recompile as it does when I switch between 32 and 64. Doesn't it just save recompile time? (and become compatable with source control)

Then again there is a caution about "Do not separate compiled code from VIs that you intend to load or run using the LabVIEW Run-Time Engine." Now I'm confused. I thought the whole point of building an application was so that it can be run on any machhine that has the RTE installed? I usually install the RTE and Drivers on a test PC and don't build a distrubution(they are so damn big). I just create a programs folder copy the exe there and run the exe file.

IT just gave me a new test PC that is running Win7x64 so I loaded LV11RTE, 488.2 with VISA and the required 64bit USB drivers for the RF power meter im using. Now I need a 64 bit version of my app to drive the whole thing. I don't really need to do the whole disturbution build do I?

[Mark_Yedinak]

We separate all of our compiled code from our source and regularly build executables for distribution. If you are building applications I don't think it matters. If however you are calling the VI dynamically and it was not included with the application when it was built (think plugins) then it will need the compiled code in order to run.

As far as your comment about why you should care if the code gets recompiled you won't have this issue if you do separate your compiled code from the source. However, if you do not you will find that every time you switch between the 32 bit and 64 bit version you will be compiling lots of code. It may prevent you from opening it in the other version. I have not tested this. Also, leaving the compiled code with the source is hell on source code control systems.

[Viper]

This is a new can of worms for me since all of my test apps are 32 bit. Now that I have to build 64 bit apps for hardware that requires 64 bit drivers on 64 bit machines it raises some questions.

1. Will I have to rebuild all of my apps to run on the 64 bit machines? (can i run 32 bit for some apps that don't controll 64 bit drivers)
2. If not will I have to have both 32 and 64 bit RTE installed to run both flavors?
3. Can I build 32 bit apps on a Win7x64 PC?
4. What other Gotcha's am I going to plow into?

Norm

[Viper]

For those that are following along. 32 vs 64 FAQ

[Viper]

I'm now getting build failures due to 488.2. Is version NI-488-2 3.1 support Win7x64. Its not clear from the download page(Windows 7/Server 2008 R2 64-bit/8/Vista/XP 32-bit/Server 2003 R2 32-bit) . I'm going to try 3.0.2 because it clearly says (Windows 7 32-bit/Vista 32-bit/7 64-bit/XP/Server 2003 R2 32-bit/Vista 64-bit/Server 2008 R2 64-bit).

Norm

[Esteban.R]

Hi Viper

As you might have read in the LabVIEW 64-Bit vs. 32-Bit Applications FAQ link

 Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development system, Run-Time Engine, and executables can be run on Windows 64-bit. 

The driver NI 488.2 3.0.2 should work in your computer, if after installing that driver and build your application you still have problems. Please post it in this forum with any error code or reference that might help in order to look for information

Regards

Esteban R.

[Viper]

After closly looking at the error message and seeing that the exe file was not going where I intended it to go I fixed the destination path and it builds. This has been an ongoing problem for LV10,11 that if the destination path gets to long the build will fail. The solution is to map a drive which will lessen the number of characters in the destination full pathname.

My reason for going x64 is on the advice of my instrument vendor to get their instrument to work with x64 Win7.

Norm

[Esteban.R]

Hi Viper

Thanks for the information.I am glad to hear that the problem is already solved. 

Regards 

Esteban R.