> I have an existing project which consists of a DLL built with BC5.
> The project contains several LIBs each of which contains the result of
> several CPP files.  These LIBs along with several 'stand-alone' OBJs
> is linked into the DLL and an import library is created from the whole
> process.  All of the functions, variables and classes which are marked
> for export show up in the import library as they should.

> Now onto BCB4.  Because of the number of source files involved, I
> would like to retain the same basic structure that I used with BC5.
> That is, each LIB will be its own project as will the DLL.  All of
> these projects will belong to a project group.  The difficulty is with
> exported functions and classes.  They are not showing up in the import
> library because they are not marked for export (marked 'public') in
> the DLL.  If I run TDUMP on one of the LIBs, all of the exported
> objects are properly marked.  If I run IMPDEF on the DLL, none of them
> show up.  How can I force the linker (or the project manager) to carry
> along the items which were exported in the individual LIBs?

> Any help would be appreciated!

>Optionally you can somehow force the linker to search for a function
in
>a lib... unfortunately the only easily accessible way to do this is
to
>call the function.

>Anduin Withers

>David Beauchesne wrote:

>> I have an existing project which consists of a DLL built with BC5.
>> The project contains several LIBs each of which contains the result
of
>> several CPP files.  These LIBs along with several 'stand-alone'
OBJs
>> is linked into the DLL and an import library is created from the
whole
>> process.  All of the functions, variables and classes which are
marked
>> for export show up in the import library as they should.

>> Now onto BCB4.  Because of the number of source files involved, I
>> would like to retain the same basic structure that I used with BC5.
>> That is, each LIB will be its own project as will the DLL.  All of
>> these projects will belong to a project group.  The difficulty is
with
>> exported functions and classes.  They are not showing up in the
import
>> library because they are not marked for export (marked 'public') in
>> the DLL.  If I run TDUMP on one of the LIBs, all of the exported
>> objects are properly marked.  If I run IMPDEF on the DLL, none of
them
>> show up.  How can I force the linker (or the project manager) to
carry
>> along the items which were exported in the individual LIBs?

>> Any help would be appreciated!

> Anduin Withers

> > While I admit it would be a nice feature it is one we do not currently
> > have (nor have we ever).

> That's strange it's always worked that way through BC5.02.