Broken arrow in compiled version

[Lentz]

Hi Forum

I have an odd issue with my LabVIEW code.

The issue is, that I have some code that runs fine in my developer version of LV 8.6. But as soon as I compile it into an .exe file and tries to run it, I get a broken arrow and a message about several missing VIs. I have tried to force a recompilation of the VIs in question and resaved them all, so the references to the VIs should be fine. And as mentioned it runs fine in developer mode. 

I have attached three screen shots below, one showing the application running in developer mode, one with the broken arrow, and one with the error messages returned. I have also tried to search both the forum and Google for the problem, but can't find any similar issues, so any suggestions would be appreciated.

Best Regards

Martin

[muks]

You have not included your subvis I suppose.

[GerdW]

Hi Martin,

it would be a great help if you could add those images unscaled or as attachment

[muks]

gerdw,

For your reference

[Lentz]

No problem, thought it was easier for people to see them directly

[GerdW]

Hi Martin,

all vis are from vi.lib, so ther eprobably something went wrong on building the executable.

Could you try to separate the problematic subvis (ReadWrite StartOptions and StartTester) and make a smaller build of them to verify the app building is ok?

P.S.: On my IE7 at work all pics were downscaled and unreadable...

[Lentz]

@MUKS

Do I realy need to include all my subVis manually when building an .exe file?  Sounds like quite a lot of work when you are dealing with large applications.

/Martin

[Cory_K]

Yes, the project needs the subVIs or a computer without the subVI's will not know how to handle the code.

When you are building the exe, go to the 'source files' menu.

Add your main VI to the Startup VI's. Add all your subVI's to 'always included'.

They should all be listed as dependencies if you use them in your top level VI, so they shouldnt be too hard to find.

[F._Schubert]

Normally, the default build process should handle it automatically for you.

But: I've seen it once in a project that SubVIs where not included. It even could reproduce it by creating a new build script. Non of them was from vi.lib, they where all my own. This was using LV 7.1 and OpenG Builder. I didn't find any explanation for it and could live with the workaround that I added all missing SubVIs as 'dynamic VIs' in the OpenG builder.

So there might be some bug lurking deep down in a hidden cave of the AppBuilder.

Felix

[muks]

---

 @MUKS

Do I realy need to include all my subVis manually when building an .exe file?  Sounds like quite a lot of work when you are dealing with large applications.

---

Yes The exe needs Proper linking with your subvis. As cory and felix has explained the build process should take care of this automatically. Did you play around with any default settings of the builder?

Message Edited by muks on 07-31-2009 01:01 PM