Subj : Re: Unresolved externals when these externals are directly or indirectly provided but not seen be the linker -- Linking incompatible targets..
To   : borland.public.cpp.borlandcpp
From : "Ed Mulroy [TeamB]" <dont_email_me@bitbuc.ket>
Date : Thu Oct 23 2003 04:13 pm

You should have been able to get almost all of this from the help, the same
place from which I learned it.

Look up the help on ilink32.exe and look at the options.  Among them are:

/Tpe  create an exe
/Tpd  create a dll
/aa  gui
/ap  console mode
/x  suppress map file
/v  generate debug info


startup code

c0d32  DLL
c0d32w  Wide char DLL
c0w32  GUI
c0w32w  Wide char GUI
c0x32  Console mode
c0x32w  Wide char console mode

runtime libraries

cw32  static linked single threaded
cw32i  import library for runtime DLL's, single threaded dynamic linked
cw32mt  static linked multi threaded
cw32mti import library for runtime DLL's, multi threaded dynamic linked

import32  import library for what Windows supplies
noeh32  library to stub out runtime type id and exception handling
   for programs which do not use them


The startup code should be the first object file listed.
The default runtime library should be the last library listed
import32 should be the next to last library listed
When using it I always make noeh32 be the first library listed

Fields left blank will be taken as the defaults.
Fields have assumed extensions
Fields not used in the link can be left unspecified.  For instance,

You might create a Hello World! style program and let the compiler figure
out how to deal with the linker.  The command for that might be this:

  bcc32 -WC -v hello.cpp

Or you might want to link it yourself.  Commands to build the program would
then be:

  bcc32 -WC -v -c hello.cpp
  ilink32 /Tpe/ap/Gn/x/v c0x32 hello,hello,,import32 cw32


In the ilink32 command line above:

The fields for the module definition file and the compiled resource file
were just left off above because they are not used.

Because the option is /Tpe the output extension defaults to .EXE

Both c0x32 and myfile in the object file field are assumed to
have an extension of .OBJ

Because the map file was not specified it is assumed to be
<output_file_base_name>.MAP, but here the /x option says to not create a map
file

Both import32 and cw32 are assumed to have the extension of .LIB because
that is the default for the field in which they are given

..  Ed

> J. Klein wrote in message
> news:3f98212b$1@newsgroups.borland.com...

.