Mac OS Universal Binary App using Labview 2009?

Is there any way to create a Mac OS app using LabView 2009 that can be run on both powerpc and intel based Macs.  I tried going through the steps found in this document (http://digital.ni.com/public.nsf/allkb/C07C01A0630​02882862571DC006C1014) - but the rosetta option was not found in the general section of the get info window...  I am wondering if this does not work for the new version of LV?
Thanks so much for your time.

The last LabVIEW version to support PowerPC Macs was AFAIK version 8.5.1. I believe 8.5 was also the first to support Intel Macs.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

  • How to open an app using LabVIEW PDA Module 7.1

    Hi,
    i´m developing an app using LabVIEW PDA Module 7.1 that needs to open a
    standard application (in particular, the default camera application) on
    my PDA (Qtek 2020 with Pocket PC 2003). Can anyone tell me how to do it?
    Thanks,
    Pedro Sampaio
    Computer and Telecommunications Engineer Student
    ESTG -IPL, Portugal

    Olá,
    Com o project podes fazer builr e deploy, a partiur daí tens a aplicação instalada na PDA.
    Cumprimentos

  • Getting Error 08 when attempting to build exe using LabVIEW 2009 (32 bit) and Windows 7

    Testing development platform on Window 7 vs XP. I received following message while building an executable using 2009 32 bit on Windows 7 machine. Same build will work on an XP machine.
    Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File permission error. You do not have the correct permissions for the file.
    =========================
    NI-488:  DMA hardware error detected.
    C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2009\errors\Internet Toolkit-errors.txt
    Any suggestions?
    Thanks

    For any who may be having this problem here is a little more information and what I did to get around the issue. (so far)
    First I tried a simple vi with a while loop in a project and made an executable build. This worked. I double checked on an XP machine the project that I was having problems with. The executable was built successfully. I changed back to the Windows 7 machine.  On the program compatibility trouble shooter I started the LabVIEW 2009 (32 bit) in the XP service pack 2 mode and selected run as administrator. The build was successful.
    Note: was logged in as administrator and program would build a simple executable in Windows 7. The executable that would not build had more complex code that included serial communication and calls to lvanlys.dll and nilvaiu.dll.
    This may not be a complete fix to the problem but at least in this one case it worked.

  • Is Pages a Universal Binary App?

    Sorry, but I can't find this info anywhere. Does Pages run native on an Intel Mac?
    R.

    Yes it is. Do a 'get info' on the file and you'll see Application (Universal) as the type.
    Eric

  • Problem about Mac Os X 10.6.3 V.S Labview 2009

    hi,labview~
    i have some problem about Labview 2009.i saw the website of NI wrote the Labview 2009 is not support for Mac OSX 10.6.3,but i have already installed it (English system) in my computer successfully.
    anyway,i cant open the programs which are wrote by labview 8.5(Japanese system) .My labmate who use Labview 2009(Mac OSX 10.5) can open those programs.
    can anyone tell me the possible reason i cant open the programs?
    Thanks a lot! 
    PS i have already tried Labview 8.5 and 8.6(English system),but the problem cant be solved.... 

    Hi mofi, my name is Taiki from National Instruments Japan.
    I assume that the link you referred to is the one below, but as you stated, LabVIEW 2009 is not supported in Mac OS X 10.6 so even though you were able to install it successfully, NI cannot assure that it will fully function on your Mac.
    LabVIEW Support for Mac OS 10.6 (Snow Leopard) and 10.5 (Leopard)
    http://digital.ni.com/public.nsf/allkb/70F17A30DE7B865E8625737F006377F8?OpenDocument
    Since you mentioned that the VI files were able to be opened on LabVIEW 2009, Mac OS X 10.5, the actual VI files should not be the issue which leaves us with the possibility of the software environment.
    You also noted that the issue could not be solved on LabVIEW 8.5 and 8.6 but was this on Mac OS X 10.6 as well?
    If so, there is a good chance that this issue is due to the fact that LabVIEW is running on an supported OS and I would suggest trying opening the files on another different Mac OS X 10.5 system.
    Unfortunately, currently Mac OS X 10.6 is an unsupported OS for any version of LabVIEW so I can only suggest trying on a Mac OS X 10.5.
    Kind regards.
    Taiki Hoshi
    Applications Engineer
    National Instruments Japan

  • Swf and Universal Binary

    I've produced a application (standalone player) on Mac for PC
    customers. It's pretty heavy, it includs videos and flash
    didactical sequences. All play fine on my 2 computers (G4 bipro
    1,25Ghz and G5 1,8 Ghz) and on the customer computers.
    But I've to install it on a MacBook Laptop (with only 512Mo)
    and then problem...
    The video and animations are slow, even if I play the swf
    separately the simple animations are slow, so I think that the
    standalone player uses Rosetta...
    How to solve that problem ?
    Is there a Flash 9 player installer (not only for browser) ?
    If I found a Flash player 9 to compile again the projector
    will it works on Universal Binary computers ?
    Thank for your help ;)

    Look like it's done! In the download page :
    http://www.adobe.com/support/flashplayer/downloads.html
    There is a link to download the INTEL version of the Flash
    Player (release and debug!). But in fact, it's a Universal Binary
    app, not just Intel !.
    So, they should flush the link for the PowerPC version...
    It's working fine on my G5 powerPC too.
    Link to the UB:
    http://download.macromedia.com/pub/flashplayer/updaters/9/sa_flashplayer_9_all_release_ub. dmg

  • Will Snow Leopard run older PPC software, pre-universal binary stuff?

    Hi there
    I know this is probably the most stupid question in the world, and I know that Snow Leopard dropped support for PPC and is intel only.
    Does this mean that I could no longer run my CS2, MS Office 2004 and Quark 6.5 (as none of these were universal binary apps, and are all written for PPC architecture)? Or is it just SL will only install on Intel macs?
    Thanks in advance

    PPC is supported, but there are some PPC applications that are too old for Snow Leopard. You should check all that you use for the latest info BEFORE updating. I think there are problems with CS2. It is not officially supported in Leopard, but may work there. CS3 is not officially supported, but does work.
    Is there a 'best' way to upgrade? clean install and retrieve data from time machine backup? Complete rebuild? Install over the top of Leopard?
    Any method should work if your applications are up to date, and your existing system has no problems. If your current system is old, though, it may have some forgotten applications or modifications that could cause upgrade problems.
    The safest way (but more work) is to erase the drive, install Snow Leopard, update to 10.6.2, copy just user accounts and data from your Time Machine backup, and install the latest versions of applications.
    If possible, make a bootable backup of your system drive before you start. That will protect you against any possible problems with the Time Machine backup.

  • Compiling a universal binary with GCC

    How would I go about building a universal binary just using gcc from the terminal? Also, how can I make it so the resulting binary can be used on other computers than my own?

    You have to add the following parameters to your compile and/or link step:
    -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -mmacosx-version-min=10.4
    This will build for 10.4 or later on Intel. If you are really sure that your code can compile with all the same settings regardless of architecture, you could add "-arch ppc" to build a universal binary. A safer alternative would be to do:
    -isysroot /Developer/SDKs/MacOSX10.3.9.sdk -arch ppc -mmacosx-version-min=10.3
    to give you a 10.3-compatible Universal Binary.
    Finally, lipo the executables together with:
    lipo -create <myapp>.ppc <myapp>.i386 -output <myapp>
    assuming, of course, that you have instructed your build scripts to append the architecture onto the end of the executable name, as in this example.
    To make sure your app can run on any machine, you could just link with static libraries. That might be difficult because most packages build dynamic libraries by default. What you can do is include your dynamic libraries with your application. MacOS X executables are actually folders with lots of files inside. Some of those files can be dynamic libraries. After you build your app, create a "Run Script" build phase to use the "installnametool" to tell the executable that its dynamic libraries are located inside its bundle. I have a more detailed write up if you want to try it.

  • How to create a dataplugin for DataFinder using LabVIEW

    We want to use LabVIEW to create a dataplugin that will be used by DataFinder (My DataFinder). We have found on the NI web site the LabVIEW DataPlugin SDK - , a SDK that allow us to create a dataplugin. The SDK is for LabVIEW 8.6.
    The dataplugin example code of the SDK work very well in the “For testing” section of the development project. We are also able to register it to use it through DataFinder. The dataplugin is available in the “Configure ...” window of DataFinder.The problem is that the dataplugin doesn’t work with DataFinder. We didn’t receive any kind of error message or code. We only get the value “eIndexedFailure” in the “Index status” property. After expectation, it seems those input parameters are different between a LV and a VBS dataplugin. And we think that can be the source of the problem. There is someone that can help us about that?
    We also want to use LabVIEW 2009. The SDK example work under 2009, but we get the same problem with DataFinder.
    Thanks
    Solved!
    Go to Solution.

    Dear Kelly R, you're right I can’t open the file in DIAdem. The RegisterLabVIEWDataPlugin.ini file is correct. But I’ve just tried to rebuild the project and then use the Installer instead of just using the Deploy. Now it works, even with my own code. Now I can open the file in DIAdem without problem. The installer uses the “NI LabVIEW Dataplugin 1.0” package. It seems that the SDK installer has never install this package.I thank you all for your help. 

  • In block diagram connecting wire getting blur while saving the VI in LabVIEW 2009

    Hello,
    I am using Labview 2009, And while I am saving  a simple VI connecting wires are getting blurry. What could be the problem?? Is it affect my program while running?
    Solved!
    Go to Solution.

    Go into Tools>>Options, select the Block Diagram page and find the section called Constant Folding. If the CF for wires check box is checked, then this is most likely the reason. You can uncheck the check box and it won't affect the way your code runs.
    If this isn't the case, you should upload an image of what it looks like.
    Try to take over the world!

  • Error in ni visa control out for usb in labview 2009

    Hi,
    I am using labview 2009 in which i have made a vi which communicates with a pic controller through USB interface.
    the vi is working fine in labview 8.6. I tried it in two PCs. but when i run that vi in a PC with labview 2009 then the VISA CONTROL OUT.vi gives error "0xBFFF003E : Could not perform operation because of i o error.". while the control in.vi works fine in both the labview versions and any other PC that i tried.
    I have run the application in total of 4 PCs with same set of cards/interfaces. two of them having labview 8.6 are running fine and giving no error but other two with labview 2009 are giving error.
    and it doesn't stop here.... i searched in the vi and did some experiment and found that when i give Request value input to control out.vi as "0x36 "(as required by my PIC program) then it is giving error but when i give other value such as " 0x35 or 34 or 55"(used for other purpose) then it is not giving error.
    Can it be a PIC programming problem? (i dont think so as everything is fine in other PC with LV 8.6)
    I have already explored the ni forum for this error solution but could not find helpful.
    Can anyone solve my problem?

    I installed labview 8.6 in that machine and made a small program with only 3 vis (visa open session, visa close session and visa usb control out.vi) which is working in LV 8.6 platform.
    Sorry the above statement is not correct actually.
    When i run the program in LV 8.6 it giving that same error but this time it is not displayed as pop up window. so i could not judge that error was still there.

  • Labview 2009 SP1 - Create exe option does not appear

    Hello everyone,
    I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other  computer with the appropiate labview run time engine).
    I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
    Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
    Thanks for advance!
    Much thanks for your time and dedication!

    I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
    The best solution is the one you find it by yourself

  • Labview 2009 I/O assistant issue

    Hi,
    I'm using labview 2009, and I can't get the I/O assistant to work-everytime I try to run it, it gives me the error message "Measurement & Automation Explorer or the Instrument I/O Assistant is not installed correctly. Please install these from LabVIEW Driver CD". I've tried uninstalling and re-installing the I/O assistant, but it's not helping-is there anything else that can cause this error I should be looking for?
    Thanks

    Hi ciwong,
    This problem usually originates from installation order. You want to install the drivers after you install after you install LabVIEW.
    Another things that jumps out is that you are listing NI VISA 488.2 as version 2.1. The current version of NI VISA is version 5 and the current version of NI 488.2 is version 2.73. 
    Please let us know if you have any questions
    Joe Daily
    National Instruments
    Applications Engineer
    may the G be with you ....

  • Can i build an application with Labview 2009 for Windows 7?

    Hello
    i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
    Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
    Solved!
    Go to Solution.

    Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
    I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application.  After installation I had to move the files from 1 location to the other to make it work.

  • Build Specifications gone with LabVIEW 2009

    I'm using LabVIEW 2009 and I still have the same problem as described in the following post (where all the answers were for older LabVIEW versions):
    http://forums.ni.com/t5/LabVIEW/build-specifications-gone/m-p/625815
    When I move a LabVIEW project from one PC to another, parts of the build specifications are gone. In the specification for the executable I have to redefine the start-up VI, the included files and the icon.
    Is this a known issue and is there a fix for it?

    Hello,
    this might be a corrupt project file. Does this only happen with this project?
    If so, then I'd suggest recreating the project and the build specifications on the original PC and trying to migrate it again to the other PC.
    Regards,
    Joseph Tagg

Maybe you are looking for