unresolved external "niScope_init" referenced from "path"

[Ceara]

 Hi,

First of all I'm sorry about my English. I'm developing a software on Builder C++ by Borland and we bought an NI DAQ 5112 PCI. I'd like to know if it's possible to use the high-level functions from niScope (such as niScope_init, _AutoSetup, _close...) on this plataform. I'm asking it 'cause I could run every example program on it whithout any problem.

[Ayman K]

Hello Ceara,

Any C based environment could be used with the NI SCOPE functions to control your PCI 5112. The NI High-Speed Digitizers Help file has the NI-SCOPE Function Reference Help that lists all the C functions that could be used. Please let me know if you have any further questions.

Ayman K

[Ceara]

   Hi Ayman K, thanks for your help.

I bought this digitalizer which brings some examples in Visual C++ based. Fortunetly, there is a tool on Builder C++ (software that I use) that converts a VC++ project in a BC++ project. When i did it with each example code, it really worked (it run perfectly as a BC++ project), of course I needed to add the NISCOPE include and library directories to my project. My problem is that when I try to use this functions (such as niScope_init, niScope_ConfigureVertical, etc...), all of them high-level functions, into my own project, a message like these below is shown:

[Linker Error] Unresolved external 'niScope_init' referenced from C:\ALUNOS\ALLAN\EVA\BUILDER2.0C\UNIT1.OBJ

[Linker Error] Unresolved external 'niScope_AutoSetup' referenced from C:\ALUNOS\ALLAN\EVA\BUILDER2.0C\UNIT1.OBJ

[Linker Error] Unresolved external 'niScope_ConfigureVertical' referenced from C:\ALUNOS\ALLAN\EVA\BUILDER2.0C\UNIT1.OBJ

[Linker Error] Unresolved external 'niScope_ConfigureVertical' referenced from C:\ALUNOS\ALLAN\EVA\BUILDER2.0C\UNIT1.OBJ

and so on

I already tried to add every include and/or library path from the example projects (that works) to my project, but it haven't worked. Now I'm looking for someone who have gotten some trouble like this. I even don't know if I'm looking it on the right way but I hope so. I aprecciate every help ok?

    Thanks a lot

              Allan Rocha

[kalyanramuv]

Hi Allan,

Can you please post the borland project you are having problem with? Also, what version of Borland C++ compiler you are using?

Kalyan

[Ceara]

Hi Kalyanramu,

I just need your email adress to send it for you

Thanks

Allan Rocha

[kalyanramuv]

Hi Allan,

You can send e-mail to support@ni.com with Attention to my name and I will take ownership of that issue as it is linked with this discussion forum post.

Thanks,

Kalyan

[Ceara]

Hi, Kalyan

I'd like to say that I've resolved this problem myself but I don't think my solution is the best one. I'm going to explain it to you and if you have
some other idea, some better idea, please let me know. I changed an especific line of my "BCBProject file" who talks about the linker
like the following:

BEFORE:

  <LINKER>
    <ALLOBJ value="c0w32.obj $(PACKAGES) Memmgr.Lib sysinit.obj
$(OBJFILES)"/>
    <ALLRES value="$(RESFILES)"/>
    <ALLLIB value="$(LIBFILES) $(LIBRARIES) import32.lib cp32mti.lib"/>
    <OTHERFILES value=""/>
  </LINKER>
AFTER:

  <LINKER>
    <ALLOBJ value="c0w32.obj $(PACKAGES) Memmgr.Lib sysinit.obj
$(OBJFILES)"/>
    <ALLRES value="$(RESFILES)"/>
    <ALLLIB value="$(LIBFILES) $(LIBRARIES) ODBCCP32.LIB UUID.LIB
NISCOPE.LIB
import32.lib cp32mti.lib"/>
    <OTHERFILES value=""/>
  </LINKER>

In different words, I just included the names of some libraries like in all "Example programs" from NI. Indeed I think there is another classic
way to say to the compiler that it is necessary to compile these libraries but while I don't discover it... My way works! Thank godness!

I apreciate your help dear friend.

Have a nice day!