How can I distribute an instrument driver in labview 8.2?

[billings11]

Since you can't build a source distribution in 8.2, does anyone have any ideas on the easiest way to distribute an instrument driver?  I have been working on copying a few hundred vi's and fixing every relative path by hand for two days.  I don't really know what to do to make this easier.  Has anyone distributed an instrument driver in 8.2 and figured out a way to do it?  I feel like jumping out of a window right now.

[Dennis_Knutson]

What exactly is your problem? You can create both an old style llb and a new style project for your driver. The source distribution option (one place where you can create an llb) is in the Project Explorer>Build Options

[billings11]

In 8.2 you can't build a source distribution with dependencies targetted to a support library. 

http://forums.ni.com/ni/board/message?board.id=170&message.id=283040#M283040

I am looking for ways to get around this.  Any ideas?  The only option I can figure is to add every single dependency vi explicitly to the project so the dependencies section is empty.  Then I can specify a target llb or folder for all of them.  But that is taking forever and is very tedious because dependencies are scattered all over.

If anyone has managed to build an instrument driver in 8.2 and made their way past this I would love to know how they did it.

Message Edited by billings11 on 01-25-2008 10:40 AM

[Amanda_H]

Hi,

Unfortunately, the best workaround is to use a different version of LabVIEW until this bug is corrected by R&D (reported as CAR #4DQ7KBRJ). I apologize for the inconvenience this causes you in building your source distribution. Good luck with your application!

[billings11]

That's not a workaround though.  Has any developer out there come up with any sort of plan for this type of thing in 8.2?  Right now I think I can distrubte the hierarchy, which will force all the dependency vi's to be distributed to their duplicate hierarchy locations.  That will at least identify and isolate all the dependencies.  Then in a completely seperate project I can add them all to the project by hand from the hierarchy distribution.  I'll see how this works out.  I've tried a coupe times but I'm still missing a couple vi's.

Message Edited by billings11 on 01-28-2008 08:35 AM