Jump to content

Make llb output optional

Recommended Posts

Hi guys,


I am trying to package a set of device drivers that are LV classes. I have each of these classes in its own LLB in the package source in order to avoid name collisions.


Unfortunately VIPM tries to put everything into a single DLL before packaging. From what I remember from OpenG package builder this is not a necessity. I understand why you do it and I have no problem with that most of the times, but could you give users the option of turning this off?




Share this post

Link to post
Share on other sites

Hello Heiko,


Thanks for the great feedback. I'm sorry for the trouble.


A work-around for this is to build each .lvlib (or lvclass) into a seperate VI Package. Would that solution meet your needs?


This issue has been on our radar and is something we're eager to fix. Having the ability to preserve the source folder structure (not put everything into a single LLB) is a good possible feature that could fix this issue.


I've created a known issue, here:




Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

By using this site, you agree to our Terms of Use.