Problems compiling C in XCODE using VISA / NI

Question

Level 1

0 points

Problems compiling C in XCODE using VISA / NI

Hi,

I'm developing a program in C to communicate with my Tektronix oscilloscope. I inherited this project from a friend (who is currently incommunicado), so I can't talk to him about it.

Basically, my problem is that my program will not build due to a linker problem. I am using functions from the NI-VISA 5.4 package for OS X 10.8. However, the linker cannot seem to find the correct functions for my system:

Undefined symbols for architecture x86_64:

"_viClose", referenced from:

_setupVI in oscilloscope.o

_getData in oscilloscope.o

_closeInstr in oscilloscope.o

"_viOpen", referenced from:

_setupVI in oscilloscope.o

"_viOpenDefaultRM", referenced from:

_setupVI in oscilloscope.o

"_viRead", referenced from:

_setupVI in oscilloscope.o

_getData in oscilloscope.o

"_viStatusDesc", referenced from:

_setupVI in oscilloscope.o

_getData in oscilloscope.o

"_viWrite", referenced from:

_setupVI in oscilloscope.o

_getData in oscilloscope.o

ld: symbol(s) not found for architecture x86_64

clang: error: linker command failed with exit code 1 (use -v to see invocation)

These are all pretty basic VISA functions. I struggled in just including the correct header file, as

#include <visa.h>

didn't work. When I went to the verbose form, it worked:

#include "/Library/Frameworks/VISA.framework/Versions/A/Headers/visa.h"

However, then the problem started happening that I'm having now -- the object linker can't find the code for the VISA functions. I've tried changing build architctures from x86_64 to just x86, without avail. I'm currently building in i386 x86. I've also tried (under Build Phases -> Link Binary with Libraries) to link the VISA.framework to the project, but this simply gives the linker error "cannot find VISA".

I feel like I am missing something very obvious. I'm still operating under the notion that either NI-VISA did not install to the correct location, or that my build settings are incorrect.

Does anyone have any insight to lend? I've been searching through different forums for help for almost 2 days now, with no avail.

MacBook Pro, OS X Mountain Lion (10.8.4), XCODE 4.6.3 (4H1503)

Posted on Aug 8, 2013 6:18 AM

Reply

Answer 1

Aug 8, 2013 7:30 AM in response to atucker-hs

Are you using Xcode or doing it from the command line?

You need to tell the compiler the library and where it is. In Xcode you would do this in the Build Phases window of the project under the Link Binary with Libraries area.

Just saw you say you tried this. Ar you sure you are setting the right path.

Where did you get the librsry from? Did you compile it on the Mac or was it compiled?

Reply

Answer 2

K T

Level 7

23,895 points

Aug 8, 2013 7:33 AM in response to atucker-hs

Option-clean to be sure there isn't any cache-glue grief involved.

Reply

Answer 3

atucker-hs Author

Level 1

0 points

Aug 8, 2013 7:34 AM in response to Frank Caggiano

The path I tried while linking the binary was the VISA.framework folder in /Library/Frameworks

In Build Settings -> Search Paths I have also specified "/Library/Frameworks/VISA.framework" for both the fields "Framework Search Paths" and "Library Search Paths".

I also have told it to include .framework directories when recursively searching.

Thanks for the suggestion though.. just unfortunately I have tried it. I feel like I'm making a really stupid mistake somewhere.

Reply

Answer 4

atucker-hs Author

Level 1

0 points

Aug 8, 2013 7:37 AM in response to K T

I just tried cleaning, but the error persists. Thanks for the idea--I hadn't thought to do that.

Reply

Answer 5

K T

Level 7

23,895 points

Aug 8, 2013 7:44 AM in response to atucker-hs

Not just 'clean' ....option-clean (sounds like a Mr. Clean ad).

Hold the option key then use the 'Product' menu - it should expand to provide a new choice, which frequently does much more than just 'clean', which seems to frequently do very little 🙂

Good luck in any case.

Reply

Answer 6

atucker-hs Author

Level 1

0 points

Aug 8, 2013 7:48 AM in response to K T

When I cleaned last time I used the key combination Command-Option-Shift-K. I tried it again using your method, but unfortunately it resulted in the same outcome.

Reply

Answer 7

xnav

Level 5

7,113 points

Aug 8, 2013 8:36 AM in response to atucker-hs

¹ 64-bit VISA applications are supported for a limited set of instrumentation buses. The supported buses are ENET-Serial, USB, and TCPIP. Logging VISA operations in NI I/O Trace from 64-bit VISA applications is not supported.

Are you only using this subset?

Reply

Answer 8

atucker-hs Author

Level 1

0 points

Aug 8, 2013 8:44 AM in response to atucker-hs

My device communicates over USB. I've also tried compiling it in an x86 environment only (which should avoid the 64 bit problem entirely... right?) and in an x64 environment. Both give me the same errors for the respective environment.

I keep coming back to the notion that the code library might not be being installed in the correct place, but that should be fixed by Link Binary with Libraries...

Thanks for the idea though. Unfortunately I've already traversed that idea as well.

Reply

Answer 9

xnav

Level 5

7,113 points

Aug 8, 2013 11:01 AM in response to atucker-hs

Did you start with this?

Reply

Answer 10

atucker-hs Author

Level 1

0 points

Aug 8, 2013 11:11 AM in response to xnav

I actually started last week using 5.3 for OS X, but ran into problems with that. I was sure my problems were coming from VISA, so I checked the site again. I updated 2 days ago to 5.4 in hopes that it would fix my problem... but sadly it did not.

tl;dr: yes.

Reply

Answer 11

xnav

Level 5

7,113 points

Aug 8, 2013 11:15 AM in response to atucker-hs

I was going to install 5.4 to see if I could help, but the package has a lot of hidden files and it is not apparent how to un-install. Did you try running the sample Xcode project from the package? Does the install include an un-install script?

Reply

Answer 12

atucker-hs Author

Level 1

0 points

Aug 8, 2013 11:33 AM in response to xnav

That is a good point that I hadn't thought of--I didn't run any install operations before installing 5.4. I'll try uninstalling all of 5.4 (there's not an uninstaller; just a text file of files to delete) and then doing a clean install after a restart. I'll let you know how it goes.

As far as their included examples, I tried to compile them both when I had 5.3 and 5.4 installed. I used gcc from the command line, and there were tons of errors - far more than I have in my XCODE project.

Reply

Answer 13

xnav

Level 5

7,113 points

Aug 8, 2013 11:40 AM in response to atucker-hs

atucker-hs wrote:

That is a good point that I hadn't thought of--I didn't run any install operations before installing 5.4. I'll try uninstalling all of 5.4 (there's not an uninstaller; just a text file of files to delete) and then doing a clean install after a restart. I'll let you know how it goes.

As far as their included examples, I tried to compile them both when I had 5.3 and 5.4 installed. I used gcc from the command line, and there were tons of errors - far more than I have in my XCODE project.

Did you try the Instruments/NI-VISA/Examples/C/ExamplesProject.pbproj?

Reply

Answer 14

atucker-hs Author

Level 1

0 points

Aug 8, 2013 11:57 AM in response to xnav

xnav, I was able to compile ExampleProject.pbproj. I'll look through that project's build settings and see if I can fix my own. I'll let you know. Thanks, because this could potentially hold the solution.

Reply

Answer 15

atucker-hs Author

Level 1

0 points

Aug 8, 2013 12:30 PM in response to xnav

Final settings I ended up using:

Architectures

Architectures: $NATIVE_ARCH_ACTUAL

Build Active Architecture Only: No

Valid Architectures: i386 x86_64

Search Paths

no Framework Search Paths

no Library Search Paths

Build Phases

Link Binary With Libraries: VISA.framework

I think keeping /Library/Frameworks in the search paths is what was causing my problems when trying to Link Binary.

Thanks to xnav and Frank (had the right initial idea, which I had tried but just in the wrong manner).

Reply