EXE with Report Generation Toolkit

[JB]

Hi,

An application which uses the Report Generation Toolkit needs several directories in the same place as the EXE : NI_HTML, NI_report and NI_Standard Report.

Is it possible to avoid this by including them in the EXE ?

Many thanks in advance

[zou]

> needs several directories

Have you tried to delete them when building exe?

You should be able to combine all folders, or simply put RGT files in the same folder of your exe.

[JB]

These directories are needed on the computer running the EXE.

[billko]

How about building an installer so you know you have everything you need?

[crossrulz]

---

@JB wrote:

Is it possible to avoid this by including them in the EXE ?

---

Yes.  You need to include the NIReport.llb and the LVClass folder from vi.lib in your project and then you can "Always Include" them in your executable's build specification.

From an old project that did this:

[billko]

---

@crossrulz wrote:

---

@JB wrote:

Is it possible to avoid this by including them in the EXE ?

---

Yes.  You need to include the NIReport.llb and the LVClass folder from vi.lib in your project and then you can "Always Include" them in your executable's build specification.

From an old project that did this:

---

You can include tool kits?  In my LV installation, License manager lists it as an add on.  I mean, yes, you can include it the way you said, but is it legal?

[crossrulz]

---

@billko wrote:

You can include tool kits?  In my LV installation, License manager lists it as an add on.  I mean, yes, you can include it the way you said, but is it legal?

---

Virtual Folder pointing to a library in vi.lib: what is wrong with that?  I am not copying any source code or anything like that (I clearly named the top virtual folder "vi.lib" for a reason).  If the add on is not installed, then the project will complain about not being able to find the file(s).  As far as including it in the EXE, that is already done with everything else you build that uses any toolkit/add on.  As long as the tool does not need a run-time license (like the Data Finder Toolkit Professional), you are fine just distributing the executable freely.

But let's take a step back to demonstrate why we have to do this for the RGT.  Somewhere in time (when is very fuzzy to me, but before 2011), the RGT was changed to use classes instead of a library.  The initialization of a report used to use a case structure based on why type of report you wanted to use.  That was replaced with dynamically loading up the desired class (Get LV Class Default Value.vi).  Since they are now loaded dynamically, the compiler cannot detect if any of those classes are used and they are therefore not automatically included (compiler needs static references).  So now you have to "Always Include" these functions.

[billko]

---

@crossrulz wrote:

---

@billko wrote:

You can include tool kits?  In my LV installation, License manager lists it as an add on.  I mean, yes, you can include it the way you said, but is it legal?

---

Virtual Folder pointing to a library in vi.lib: what is wrong with that?  I am not copying any source code or anything like that (I clearly named the top virtual folder "vi.lib" for a reason).  If the add on is not installed, then the project will complain about not being able to find the file(s).  As far as including it in the EXE, that is already done with everything else you build that uses any toolkit/add on.  As long as the tool does not need a run-time license (like the Data Finder Toolkit Professional), you are fine just distributing the executable freely.

But let's take a step back to demonstrate why we have to do this for the RGT.  Somewhere in time (when is very fuzzy to me, but before 2011), the RGT was changed to use classes instead of a library.  The initialization of a report used to use a case structure based on why type of report you wanted to use.  That was replaced with dynamically loading up the desired class (Get LV Class Default Value.vi).  Since they are now loaded dynamically, the compiler cannot detect if any of those classes are used and they are therefore not automatically included (compiler needs static references).  So now you have to "Always Include" these functions.

---

Thanks for the information!  I have to admit that I never build an executable without an installer to go along with it, so I never pay attention to what is actually added in with the installer and what is included in the executable.  There was a time - pre- LV 2012? - when you had to pay attention to all that, but I've since grown dependent on LV sorting all that out for me.  😞

That, with the realization that I'd never seen the RGT in a compiled executable before probably means I had no business even replying to this topic.  But at least I gained some EXP in both knowledge and humility.

[JB]

---

---

Yes.  You need to include the NIReport.llb and the LVClass folder from vi.lib in your project and then you can "Always Include" them in your executable's build specification.

---

Thank you for your answer.

Unfortunately this doesn't work (at least in my case) and the directories are still needed by the EXE. If I delete them (in same location as EXE), a dialog box appears when launching the EXE to search for all these VIs. Obviously, they are not included in the EXE.

Have I missed something obvious ?

[crossrulz]

---

@JB wrote:

Have I missed something obvious ?

---

Yes.  You did not include the LVClass folder in your executable.  Look closer at the image I posted earlier.