Jump to content

Sara

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Hi Ashish, So... I guess there is no workaround for this. I will add a note in our Release Notes about thos. Thanks, Sara
  2. Hi, I've created a package using VIPM 2014, but I cannot install it in another machine that uses VIPM 2013. Is this expected? If so, is there a workaround for this? Thanks, Sara
  3. Hi Ashish, Thanks for your answer. Using the System target is not the best approach for us. We are developing a library that will work on several platforms. We were planning to create a VI package for each platform that will contain the board files (so NI MAX can install the library in the board) and a LabVIEW project as an example on how to use the library. For the files for NI MAX, we could go with a System target. The LabVIEW project, on the other hand, needs to be installed in <LabVIEW version>/examples. For that, we need to use the LabVIEW target when generating the package. Is there a workaround we could use? Thanks, Sara
  4. Hi, I am building a VI package with the VIPM 2014 that contains a LabVIEW 2013 project (.lvproj) and some support files, but no VIs. This used to work in older versions of VIPM, but it is not working now. I get an error saying: "You're trying to build a package using LabVIEW as your target but there are no LabVIEW compatible files in the source folder you selected. Please try another source folder o switch to using the System target" Is there any workaround for this issue? Thanks, Sara
  5. Hi Jim, Thanks for the suggestions. That's what I was looking for!! All the best, Sara
  6. Hi, I would like to be able to build our VI package from command line as part of our automated build process. I have created a .vipb file with the configuration. Is there a way generate the package from command line using that .vipb file? Thanks, Sara
  7. Hi, Currently, we have a package called company-name_package_name-<version>.vip . I want to create a new package for the ARM support. My idea is to have the name to be company-name_package_name_arm_support-<version>.vip. However, VIPM is changing the package filename to be company_name_package_name_arm_support-<version>.vip. Is there a way to prevent this change? Thanks, Sara
  8. Hi, I having exactly the same error with LabVIEW 2013 and CentOS 2.0. I installed the LabVIEW RT 2009 package but didn't fix this. I'm running as root. Any fix for this? Thanks! ./source/lib/IntelDataCollector.cpp(2332): CPUID(2) returned unrecognized cacheID of 63. ./source/lib/IntelDataCollector.cpp(2332): CPUID(2) returned unrecognized cacheID of 76. ./source/lib/IntelDataCollector.cpp(2323): Abandoning cache enumeration from CPUID(2). Using CPUID(4) instead. ./source/lib/IntelDataCollector.cpp(2332): CPUID(2) returned unrecognized cacheID of C1. ./source/lib/IntelDataCollector.cpp(1013): Intel: CPUID(4) cache results did not all merge with CPUID(2). ./source/lib/IntelDataCollector.cpp(1105): Inconsistent L2 cache information. Searched for: ./source/lib/IntelDataCollector.cpp(1108): level: 2, role: 2; type: 0, entryType: 2, entrySize: 64, size: 262144, associativity: 8 ./source/lib/IntelDataCollector.cpp(1110): Raw data was: eax: 00000000, ebx: 00000000, ecx: 01006040, edx: 00000000 ./source/lib/IntelDataCollector.cpp(1111): L2 cache data from CPUID(2), CPUID(4) and CPUID(0x80000006) report a mismatch. ./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update. ./source/lib/IntelDataCollector.cpp(985): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update. ./source/lib/IntelDataCollector.cpp(976): CPUID(4) provided cache that CPUID(2) did not. Intel cache parse may need an update. LabVIEW caught fatal signal 9.0.1 - Received SIGSEGV Reason: invalid permissions for mapped object Attempt to reference address: 0x0x9b5cf4f Segmentation fault
  9. I've just tried using VIPM 2012 and it's the same problem. I've even tried deleting the palettes and regenerating them again... but it's still not working
  10. Thanks again, Ashish. But we are finishing the release and I cannot send the source folder right now. I'll take into account for the future
  11. Ashish, Thanks for your answer. The Palette is generated correctly. I've got all the subpalettes etc. The problem is the "Show in palette" button in the VIPM once I install the vip. When I click on it, it opens one of the subpalettes
  12. I have created a package using the VIPM 2011 with multiple examples organized in subfolders and several subpalettes with a common main palette. When I install the newly created package, however, the "Show in Palette" button shows one of the subpalettes and "Show Examples" shows one of the subfolders. Any idea on how do I fix this? Thanks!!
×
×
  • Create New...

Important Information

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