LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
TiTou

Allow App build specs for different OS in the same project

Status: New

Use case :

I work on a multi-plateform project and I compile the same application for Windows, Linux desktop and NI Linux RT

 

Currently I have 3 different lvproj, on for each OS I build my app for.

 

It would make life much easier if LabVIEW would allow me to have - in the same lvproj - app build specs for different OSes.


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

6 Comments
wiebe@CARYA
Knight of NI

This is mentioned here: Build 32-bit executable in 64-bit IDE - NI Community

 

Although the idea is to support 64 bit on 32 bit, cross OS compiling is mentioned. Not sure if that makes this one a duplicate, but kudo-ing the other idea might have results faster. 

TiTou
Trusted Enthusiast

Well the idea you mention is going much further : compiling a OSX/Linux App from Windows, not that I wouldn't like that, but realistically...

All I'm asking is for LabVIEW on any OS to be able to keep - and not alter - build spec that are for other OSes to avoid having to maintain one lvproj per OS.

To me it sounds quite trivial compared to the other one.


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

TiTou
Trusted Enthusiast

and no wonder I forgot about the idea you mentioned, I kudoed it in march 2012...

TiTou_0-1634741762235.png

 

 

so when you say "kudo-ing the other idea might have results faster." well, really?


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

wiebe@CARYA
Knight of NI

Ah, I now see what you mean with the idea.

 

You simply want projects to allow multiple build specifications, so that you can use 1 project and open\compile on multiple targets.

 

That sounds a lot easier. It could be a good step towards cross compiling. +1

TiTou
Trusted Enthusiast

sorry if the original description isn't clear enough


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

rolfk
Knight of NI

Well at least for LabVIEW realtime targets that definitely already works. I typically have one project consisting of both the the "My Computer" target which contains the Windows host application and the specific "cRIO" target to contain the according realtime (and usually FPGA) code.

 

Depending on how much platform specific code you use and how you integrate it in your application (conditional compile structure is your friend here), you can also use the same "My Computer" target for all the LabVIEW desktop versions, but obviously won't have support for real-time targets on non-Windows LabVIEW versions (they show up as a yellow question mark when you open the project on LabVIEW for Linux or Mac OSX, the same as when you open them on a Windows version without LabVIEW Realtime and CompactRIO installed).

 

Things completely change however if you start to use Packed Libraries. Then you need to have different projects for every platform you want to support or you are rather sooner than later losing all your hairs!

Rolf Kalbermatter
My Blog