Discussion:
Linker error: Unresolved external
(too old to reply)
JackM
2008-07-10 16:58:57 UTC
Permalink
Hello Borland Group!
I am using CppBuilder and getting an Linker error: "Unresolved
external FT_Open()"
The problem began when I added the function FT_Open() in my
unit1.cpp.
I believe the function declaration is located in FTD2XX.h but the
compiler cannot find it?


I tried to add FTD2XX.H and FTD2XX.lib to my working project by doing
the following:

1. Placed a copy of FTD2XX.H and FTD2XX.lib in my working directroy
with unit1, unit2, etc....
2. Placed a copy of FTD2XX.H and FTD2XX.lib in C:\Program Files\Borland
\BDS\4.0\lib
3. added line of code in unit1.cpp------> #include FTD2XX.H
4. edit--> Projects-Options-C++Compiler-Paths and Defines:
added path where the FTD2XX.lib file is
located
5. edie--> Projects-Options-Linker-Paths and Defines:
added path where the FTD2XX.lib file is
located
6. I have also tried adding the FTD2XX.lib file directly by using the
add-file option but this produced another set of error messages.

Thank you for any help!
Jack Mc
JackM
2008-07-16 15:00:56 UTC
Permalink
Post by JackM
Hello Borland Group!
I am using CppBuilder and getting an Linker error: "Unresolved
external FT_Open()"
The problem began when I added the function FT_Open() in my
unit1.cpp.
I believe the function declaration is located in FTD2XX.h but the
compiler cannot find it?
I tried to add FTD2XX.H and FTD2XX.lib to my working project by doing
1. Placed a copy of FTD2XX.H and FTD2XX.lib in my working directroy
with unit1, unit2, etc....
2. Placed a copy of FTD2XX.H and FTD2XX.lib in C:\Program Files\Borland
\BDS\4.0\lib
3. added line of code in unit1.cpp------> #include FTD2XX.H
                           added path where the FTD2XX.lib file is
located
                           added path where the FTD2XX.lib file is
located
6. I have also tried adding the FTD2XX.lib file directly by using the
add-file option but this produced another set of error messages.
Thank you for any help!
Jack Mc
Later:
I found I was using the wrong FTDI drivers for this USB chip! There is
a seperate set of FTDI drivers for Microsoft compiler and CppBuilder
compiler. Obviously with the Borland compiler I should have used the
FTDI drivers for CppBuilder. The FTDI web site has the correct drivers
(source code) for CppBuilder to operate this USB chip. Problem solved.
Loading...