question about license

[ztyaner11]

I want to sale my software based on Labview, is that legal if I build it as an independent application program and what kind of system should I need to build applications?

But it seems that it doesn't work well when I build it as an independent application program cause in my program I need to read a file in a relative path which is based on the installation path, so how can I get the installation path in my program?

[mikeporter]

Check with NI about the licensing issue. Concerning the path question, there's a primative path constant for the current VI's path. In a built application the path it returns will be something like:

c:/program files/myApplication/myApp.exe/myVI.vi

Strip this path twice and you have the directory where the executable is installed.

Mike...

[LV_Pro]

To build applications in LabVIEW you will need either the Professional Development version, which includes the Application Builder, or you will need to purchase the labVIEW add-on toolkit version of the Application Builder. With that you can create "*.exe" versions of your program which may be distributed. For them to run you will need the LabVIEW runtime engine, which the application builder will include in the distribution files (if directed to), which may be freely distributed. It (the runtime) is a fairly large program (10Mb+ ?) and this fact is frequently pointed out by my Visual Basic/Visual C++ friends, but I then point out that their code also requires a runtime, it just comes preinstalled in the bloated Windows installation.

Mike is correct (as he frequently is) about stripping the paths differently between built applications and development versions.

How did you discover this if you weren't aware of application builder?

P.M.