Jump to content

Search the Community

Showing results for tags 'bug'.


More search options

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Forums

  • General Discussion
    • General Discussion
  • VI Package Manager (VIPM)
    • VI Package Manager (VIPM)
  • JKI Tools
    • JKI State Machine
    • JKI State Machine Objects (SMO)
    • Caraya Unit Tester
    • VI Tester
    • JKI JSON
    • HTTP REST Client
    • JKI Simple Localization
    • EasyXML Toolkit
  • Legacy Tools
    • Legacy Tools

Calendars

There are no results to display.

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Joined

  • Start

    End

Group

AIM

MSN

Website URL

ICQ

Yahoo

Jabber

Skype

Location

Interests

Found 2 results

  1. RDR
    When selecting to build a package for only LabVIEW 64-bit, the package is still displayed in my repository when installing to 32-bit LabVIEW. I noticed in the spec file for the packages there is a tag for: Exclusive_LabVIEW_System="ALL" I assume this is the value intended for 32 or 64-bit LabVIEW, but I do not see this tag update no matter what changes I make to the LabVIEW bitness. I am using the latest version of VI Package Manager Pro (2014.0.2). Kind regards, -R
  2. RDR
    When selecting to build a package for only LabVIEW 64-bit, the package is still displayed in my repository when installing to 32-bit LabVIEW. I noticed in the spec file for the packages there is a tag for: Exclusive_LabVIEW_System="ALL" I assume this is the value intended for 32 or 64-bit LabVIEW, but I do not see this tag update no matter what changes I make to the LabVIEW bitness. I am using the latest version of VI Package Manager Pro (2014.0.2). Kind regards, -R
×
×
  • Create New...

Important Information

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

  I accept