Subj : Re: Unresolved reference __turboFloat
To   : borland.public.cpp.borlandcpp
From : It's me
Date : Sun Dec 05 2004 07:55 pm

Thanks to both Greg and Ed.  I finally got it to work.  The verdict appears
to be:

a) ilink32.exe doesn't appears to recognize what's in ilink32.cfg (whereas
bcc32 without the -c option does) when I use the command line to invoke it.
I had to specify the -L option at the command line or else it can't find the
libraries.

b) As you guys pointed out, the documentation is wrong in saying that you
can have multiple -L options.   I changed it to the semicolon form and it
works.

***HOWEVER***.  If I use the response file format, ilink32.cfg appears to be
recognized.   For example, if I issue the command:

   ilink32 @abc.lnk

where abc.lnk contains:

===================
c0x32+abc
abc

mylib.lib import32 cw32
===================

with "abc" the name of my prgram, and mylib.lib is my own library that's
sitting elsewhere.

Then I can have an ilink32.cfg like this:

===================
-ltWC
-ap
-c
-x
-Gn
-Tpe
-L(path of my own library);E:\Borland\Bcc55\lib
===================

This works.

If I don't use the response file, then I have to have the -L option as part
of my command line, or else it won't work.

Now on with the chanllenge of dll creation...see separate posting.

Thank you everybody.  I wished I had kept my complete set of  Borland C
compiler documentation from long long ago....

----
It's me



"Greg Chicares" <chicares@mindspring.com> wrote in message
news:41b3869b$1@newsgroups.borland.com...
> On 2004-12-05 11:01 AM, Ed Mulroy [TeamB] wrote:
> >
> > While the compiler will accept multiple -I statements and
> > combine them I do not know that the linker will do that for
> > multiple -L statements.
>
> Well, bc++5.02 online help for '-L' says:
>
>    You can place more than one of each option on the
>    command line, like this:
>      BCC.EXE -Ldirname1 -Ldirname2 -Iinc1 -Iinc2 -Iinc3 myfile.c
>    If you list multiple -L or -I options on the command line,
>    the result is cumulative; the compiler searches all the
>    directories listed in order from left to right
>
> But that's wrong and you're right. My personal documentation says:
>
> # Contrary to the borland documentation, library paths
> # *must* be given as
> #  /L$(bc_owl_path)/lib;$(bcXXXdir)/LIB \
> # i.e. a single '/L' option with paths separated by a semicolon.
> # This option:
> #  /L$(bc_owl_path)/lib /L$(bcXXXdir)/LIB \
> # will *not* work, even though the documentation says it will. It seems
> # that the last '/L' option *replaces* any preceding '/L' options.
>
> > Assuming that there are 3 desired
> > paths to search for libraries and they are path1, path2 and
> > path2 then I would expect to see
> >
> >   -Lpath1;path2;path3
>
> That works.
>
> > and not
> >   -Lpath1
> >   -Lpath2
> >   -Lpath3
>
> That does not work.

.