Subj : Re: Linking libraries...
To   : borland.public.cpp.borlandcpp
From : Ed Mulroy [TeamB]
Date : Thu Apr 29 2004 06:05 pm

My guess is that your program is C++ and your library is C.

C++ constructs public names for functions differently than C so when
you include the header files for the BPIB interface C++ places a
symbol of what to call into the object file using the C++ scheme and
that doesn't match that the C items provided by the library.

If that is the case then this will solve it.

In the header file:

-------------start of header file---------
#ifdef __cplusplus
extern "C" {
#endif

---------current contents of header file-------

#ifdef __cplusplus
  }
#endif
-------------------end of header file-----------

The change will not alter the header file's ability to work with C
programs.

..  Ed

> Jason Schierling wrote in message
> news:40916168$1@newsgroups.borland.com...
>
> I have a somewhat large application that uses a GPIB interface.
> Everything compiles correctly, but i get a bunch of linking
> errors when I try to make the .exe.  The errors say "Undefined
> symbol "xxx" in module "xxx".  I am including the correct header
> files and the library path is correct in the project settings.
>
> I am using Borland 4.5 under Windows 98.  The application is
> 16-bit.
>
> Any help would be appreciated.

.