7c7
Subj : 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 : "J. Klein" <jkl76a@yahoo.com>
Date : Thu Oct 23 2003 12:42 pm

When one links with "Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland" one needs to indicate which "startup" to use or be content that some default provided by linker will be correct.

Syntax

ILINK32 [@respfile][options] startup myobjs, [exe], [mapfile], [libraries], [deffile], [resfile]


startup 
    A Borland initialization module for executables or DLLs that arranges the order of the various segments of the program. Failure to link in the correct initialization module usually results in a long list of error messages telling you that certain identifiers are unresolved, or that no stack has been created. Perhaps some of these object files located in LIB directory qualify as an initialization module but,
                               what are the rules for which one to chose?
        c0d32.obj
        c0d32w.obj
        c0d32x.obj
        c0s32.obj
        c0w32.obj
        c0w32w.obj
        c0x32.obj
        c0x32w.obj
        fileinfo.obj
        gp.obj
        wildargs.obj
                               And, do one of the above predicated use of specific libraries?

        cw32.lib
        cw32i.lib
        cw32mt.lib
        cw32mti.lib
        dxextra.lib
        import32.lib
        inet.lib
        noeh32.lib
        ole2w32.lib
        oleaut32.lib
        uuid.lib
        wininet.lib
        ws2_32.lib

Perhaps there is a documentation on this somewhere. Can someone direct me to it?

Also, I presume that the compiler can produce different type of executable that will correspond to one of the above initialization modules. What are these type and how does one indicate to the compiler on the command line which one to produce?

Thanks.

.

0