Thanks Robert, Unfortunately i think i painted the wrong picture in the earlier message. I am infact writing the DLL and shared library in C. I have all the code and it compiles on both the Mac OS X using Code Warrior and Visual Studio 6 on the PC. The PC version i can access and see the exported symbols / functions, but on the Mac i can not. Even building some of the sample shared librarys leaves me with no exported functions to call from labview. I have tried using the ".exp" file, and also the "#pragma export on ...etc" but this just changed nothing. I suppose the essents of this question is how exactly does LabView expect the functions to be exported. And what language or "stationery" is the best choice in CodeWarrior / Apple X Code. I did find examples of the CIN projects, so i think i will try and modify one and see how that compiles and if Labview can see the exported functions.
Thanks, Carl Pattie "Robert M" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Hello Carl, It looks like you are having trouble writing DLL files using LabVIEW on Mac OS X. I believe they now call them frameworks under OS X. First, let's make sure you have the necessary software. I'm assuming you already have the <a href= http://sine.ni.com/apps/we/nioc.vp?cid=10732&lang=US >LabVIEW Application Builder for Mac OS</a>. Under Mac OS 9, you needed to download MPW (Macintosh Programmer's Workshop) in order to write dll's in LabVIEW. The OS X version of this is called the Project Builder. <a href=http://zone.ni.com/devzone/conceptd.nsf/webmain/5DF85B448EB081D8862568F F006A0B20?opendocument>This </a>tutorial is made for Windows, but it should be almost identical for a Mac. I just tested making a dll file on Mac OS X, and it seemed very similar to the process on Windows. Let me know how far these suggestions get you, and if you need additional help, I'll be happy to look further into it. Have a nice day! Robert M Applications Engineer National Instruments
